The difference between a U disk and a solid-state drive

one of the gaps between U disk and SSD: storage speed

In fact, in theory, the U disk as a solid-state hard disk to use is not not, for example, now some versions of the Linux system to support the system installed to the U disk, which runs on a U disk, such as the U disk disguised as a solid-state drive. But once the U disk as a solid-state drive as a system disk to use, there is the biggest problem, that is read marry write speed too slow! This is mainly because of the USB disk and solid state drive between the master chip, the number of flash particles and cache capacity caused by different. In particular, the solid-state hard disk uses a number of flash particles, and its internal is similar to the use of RAID writing, can simultaneously on different particles to write or read data, so performance is extremely 慓. and the U disk is usually a single channel to write, so there is no way in the performance and solid-state hard disk compared. In addition, in the cache, solid-state drives generally have 32M or more capacity to store data, and the vast majority of U disk does not have a buffer, so the performance also caused a considerable difference.

　　The gap between U disk and SSD: service life

In addition to the huge difference in speed, the main control of U disk is also mostly do not have the average write data function. What is the average write data? Simply put, the flash disk and the solid-state drive have a certain number of write life. Once the number of writes has reached this amount, it is no longer possible to write data, which means the damage to a U disk or SSD.

As we all know, if as a system disk, the number of data written every day will be many, so the main control chip of solid state hard disk has an average write data algorithm to prolong the service life. Simply put, if there are 10 blocks of data in a solid-state drive (small note: Just for the convenience of example, in fact, far more than 10 blocks of data, when we write data repeatedly, in order to ensure that 10 pieces of data have the same number of writes, so even if each block of writing only 10 times, In theory, the number of blocks that cannot be written will appear only after 10 of the 10 times.