2 ms·
This is caused by the emmc storage inside getting slower due to wearing out. emmc firmwares are universally crap at wear levelling, so after a few years use a
by londons_explore 4y ago
This is caused by the emmc storage inside getting slower due to wearing out. emmc firmwares are universally crap at wear levelling, so after a few years use a card that could read/write data at 200 Mbytes/sec before might now be as low as 2 Mbytes per second for reading the most read/written sectors.
The effect is compounded by the fact that modern apps are larger, taking up more RAM and flash storage. That in turn means the emmc has to work much harder - since there will be less free RAM for caching, there will be far more random reads.
The overall effect is a huge storage slowdown that makes the device unusable.
- mnw21cam 4y agoI just benchmarked the storage on my phone, and it seems fine. But I'm guessing the benchmark doesn't touch the most heavily-worn parts of the storage.
- mnw21cam 4y agoIs there an app that can tell me the wear stats from the storage device? A bit of googling tells me that a service called storaged processes them, but I can't immediately find an app that does this.
- londons_explore 4y agoI don't think either android or iOS expose this info to apps. You might be able to get it from a rooted device - although if it is emmc based storage, then there isn't even a standard way for the OS to know - it depends on the manufacturer of the device using proprietary calls (if it collects stats at all).
- joshspankit 4y agoThe underlying “now” test seems reasonable: load a bunch of data off the storage and see how long it takes. You could even theoretically read all data and uncover slow sections (if there is such a thing). Writing would be harder of course.