Quote:
Originally Posted by Ian.M
FLASH memory cell degradation with use affects reliability, not response time. Any application level slowdown is due to filesystem fragmentation or poorly thought out indexing schemes. If you want the truth, straight from the horse's mouth, look at the technical briefs and application notes on various FLASH memory manufacturers websites.
Amazon claim you can turn an eInk kindle off by holding the power button for up to eight seconds depending on model. From personal experience, a K3 that has been shut down that way, cold boots when next activated, and if it is left unused, the battery seems to retain its charge for longer.
|
If you're referring to my post, you misunderstood it, or you need to go back and read it again.
I'm not talking about reliability, which is related, but performance.
Writes are done as per blocks basis on flash storage, not cell. So if you need to write a partially filled block , the system has to erase all cells on that block via programming and that operation takes time (single cells cannot be erased independently). That only happens when the storage (available blocks) is getting full or you're running out of free blocks, which is thousands of ebooks on a Kindle, depending of ebook size.
Also, because there are no mechanical parts on flash storage, fragmentation, while exists, is negligible. That's why you should never defrag Windows if it's running on a SSD drive, besides it reduces the drive's life.
I've own like 4 different Kindles in my life, except 1st gen. None of them have shown any reduction in reading speed over the time. This is because filling the Kindle with books and keeping those there mainly requires reading activities, not a full reprogramming of a whole block and reading is fast on a flash storage.