On 10/04/18 22:53, Vir Campestris wrote:
SSDs _do_ have one problem spinning rust discs don't, but you rarely see
it - if you write a _LOT_ of data they can run out of spare blank space
to write to, and they have to slow down while they clean a bit more. The
trim command (hi John!) is designed to let it know about free space it
can erase in advance.

This is more or less ********.

SSDs can only write ENORMOUS blocks at a time.

So changing one bit on a file will, in the end, result in maybe 10K
bytes of write., normally to a fresh block to minismise wear which is
all down to writes.

This is not down to how MUCH data is written, but simply to how often it
happens.

In practive modern SSDS have a lot of cache RAM inside, to minimise
writes, and of course modern operating systems (even Windows) will also
cache writes in RAM.

What this means is that lost of data does not slow down SSDS at all.
Only if all the cached writes in the disk and the operatinsg system get
full will the disk actually write anything at all, and SSD writes are FAST.

Since they are done in HUGE chunks.



--
A lie can travel halfway around the world while the truth is putting on
its shoes.