Има некоја процедура за прво користење на ССД, или плаг и плеј?
Плус, дали е подобро миграција на системска партиција или инсталација одново?
Ако добро ме држи памтењето, наводно миграција некогаш можело да не ја вклучи
TRIM функцијата и да има проблеми со
Garbage Collection (дури и кај новите ОС-и). Како и да е, нема да ти шкоди да го пролисташ ова:
http://www.overclock.net/t/1156654/seans-windows-7-install-optimization-guide-for-ssds-hddsи ова за основните работи:
http://www.overclock.net/t/1179518/seans-ssd-buyers-guide-information-threadИ една важна работа што ја спомнав пар пати (за оставање неискористен, дел од ССДто), ама никој не ја прокоментира:
Over-provisioning:
Over-provisioning (sometimes spelled as OP, over provisioning, or overprovisioning) is the difference between the physical capacity of the flash memory and the logical capacity presented through the operating system (OS) as available for the user. During the garbage collection, wear-leveling, and bad block mapping operations on the SSD, the additional space from over-provisioning helps lower the write amplification when the controller writes to the flash memory.
When an SSD is almost full, this could cause problems. Even for writing a small amount of data you need an completely empty block. For this reason SSDs have over-provisioning, which means more storage capacity present than is available. That this is possible without making consumers feel cheating is thanks to manufacturers of traditional hard disks.
1. The first level of over-provisioning comes from the computation of the capacity and the use of units for gigabyte (GB) where in fact it should be written as gibibyte (GiB). Both HDD and SSD vendors use the term GB to represent a decimal GB or 1,000,000,000 (10^9)bytes. Flash memory (like most other electronic storage) is assembled in powers of two, so calculating the physical capacity of an SSD would be based on 1,073,741,824 (2^30) per binary GB (GiB). The difference between these two values is 7.37% ((2^30-10^9)/10^9). Therefore a 128 GB SSD with 0% over-provisioning would provide 128,000,000,000 bytes to the user. This initial 7.37% is typically not counted in the total over-provisioning number. A 500 GB hard disk only has 466 GB available, also referred to as GiBs. A 256 GB SSD has 256 actual gigabytes (GiBs), but keeps 7.3 percent from being available to the OS. The rest is reserved for over-provisioning to make the controller more efficient.
2. The second level of over-provisioning comes from the manufacturer. This level of over-provisioning is typically 0%, 7%, or 28% based on the difference between the decimal GB of the physical capacity and the decimal GB of the available space to the user. As an example, a manufacturer might publish a specification for their SSD at 100 GB, 120 GB or 128 GB based on 128 GB of possible capacity. This difference is 28%, 7% and 0% respectively and is the basis for the manufacturer claiming they have 28% of over-provisioning on their drive. This does not count the additional 7.37% of capacity available from the difference between the decimal and binary GB. SSDs with a SandForce controller have 256 GB worth of memory chip capacity, but are sold as 240 GB SSDs and make 223 GB available to the OS. That's 12 percent of over-provisioning.
3. The third level of over-provisioning comes from end users to gain endurance and performance at the expense of capacity. Some SSDs provide a utility that permit the end user to select additional over-provisioning. Furthermore, if any SSD is set up with an OS partition smaller than 100% of the available space, that unpartitioned space will be automatically used by the SSD as over-provisioning as well. Over-provisioning does take away from user capacity, but it gives back reduced write amplification, increased endurance, and increased performance. It is basically the same a "short stroking" a mechanical HDD. For example. You have a 128GB drive. You decide that you are going to format your primary partition to 120GB and leave the remainder of the drive "unallocated". This will leave an additional 8GB of, "ready to be written to", space that the drive will use for over provisioning. There is also an ATA command that can be used to set this space, but it is just easier to not use all of the space of the drive while partitioning.
Even so user over provisioning via partition size is counterproductive. Users should not need to do this, all they are doing is wasting usable space on the drive. Normal consumers do not need to protect from wear and tear. They are not doing a ton of write amplification. Modern controllers, like SandForce, lower write amp in write in half. It is meant to give a larger backup of NAND in case of cell failure for server SSDs doing, for example, over 10,000 writes in a day.
The only reason to do it on a consumer level I can think of is to make sure you do not fill up the whole drive with data so you can have some spare if you do fill it up. Even then there is still that ~7% from the first level talked about earlier.
