One of the common complaints late in the life of the original Nexus 7 was slow storage I/O performance, leading to an inconsistent user experience. After a fresh flash, the Nexus 7 was speedy and performant, but after months of installing applications and using the tablet, things began slowing down. This was a friction point that many hoped would be fixed in the new Nexus 7 (2013) model, which it was. There’s even more to the story though, it turns out Google has fixed that storage I/O aging problem on all Nexus devices with the Android 4.3 update.

In our Nexus 7 (2013) review, I talked about how I had confirmed that Android 4.3 onboard the device had enabled support for fstrim, an application which TRIMs blocks not in used by the filesystem. TRIM is essentially the paging channel through which the OS tells an SSD or eMMC controller that a block is no longer in use, and thus ready for garbage collection. This is critical for maintaining performance on the controllers in use across smartphones and tablets and preventing aging-related I/O performance slowdown.

Remember that deleting a file in software isn't actually communicated to solid state storage (whether SSD or eMMC). The space is freed up from the user's perspective, but the eMMC controller in this case still treats the pages in NAND as having valid data. Let's say you copy a 3GB movie to your internal storage, watch the movie and later delete it. You'd have 3GB free to re-use, but until you re-write those blocks the eMMC controller would treat all 3GB as valid data. There's a data structure used by the eMMC controller that tracks mapping logical locations to physical locations in NAND. I won't go into great detail here but the more complex that mapping becomes, and the more locations that have to be tracked, the slower internal NAND management works.

TRIM (and its equivalents) establishes that communication between file system and eMMC/NAND controller. When unused blocks are TRIMed at the OS level, a signal is sent to the eMMC controller telling it that it no longer has to track that data. A good controller will then schedule those NAND pages/blocks for garbage collection/recycling, thus improving performance. Note the use of the phrase "good controller". Enabling TRIM support is most definitely the first step though.

Although I had searched for direct confirmation before posting the Nexus 7 (2013) review, and had found some references to it, a reader of ours found fstrim inside vold (the volume daemon) and the notes essentially describe what I’ve said already.

I’ve learned a bit more on the conditions underlying when Android 4.3 will TRIM filesystems, as it wasn’t completely clear before. The Android framework will send out a “start idle maintenance window” event that the MountService listens for, and then invokes vold to fstrim filesystems when a few conditions have been met – the device hasn’t been touched for over an hour, no idle maintenance window event has been sent in 24 hours, and the device is either off-charger with 80% battery or on-charger with 30% battery. The goal is to have fstrim run roughly once every 24 hours if you’re in the habit of plugging the device in to charge every night.

Fstrim sends the FITRIM ioctl() command to all writable filesystems when invoked, which discards (TRIMs) blocks on the eMMC not used by the filesystem. Without TRIM the controller will track blocks that have data deleted by the filesystem, but the controller still believes has data it needs to track. TRIM is the signaling pathway through which the filesystem and OS can tell the controller that it can now consider those blocks unused and for garbage collection – different controllers will behave differently since it’s their prerogative to decide what happens next however.

It’s also easy to check and see that fstrim is running on devices over adb, by running and looking for it:

adb logcat -d | grep -i fstrim

Example output from a few Nexus devices I have handy which have been on for over 24 hours and have the Android 4.3 update installed.

Nexus 7 (2013)

┌─[brianklug@MBP] - [~/Downloads/APKs] - [Mon Jul 29, 03:30]

└─[$] <> ./adb logcat -d | grep -i fstrim

I/fstrim ( 172): Starting fstrim work...

I/fstrim ( 172): Invoking FITRIM ioctl on /cache

I/fstrim ( 172): Trimmed 564789248 bytes on /cache

I/fstrim ( 172): Invoking FITRIM ioctl on /data

I/fstrim ( 172): Trimmed 25105637376 bytes on /data

I/fstrim ( 172): Invoking FITRIM ioctl on /persist

I/fstrim ( 172): Trimmed 0 bytes on /persist

I/fstrim ( 172): Finished fstrim work.

I/fstrim ( 172): Starting fstrim work...

I/fstrim ( 172): Invoking FITRIM ioctl on /cache

I/fstrim ( 172): Trimmed 0 bytes on /cache

I/fstrim ( 172): Invoking FITRIM ioctl on /data

I/fstrim ( 172): Trimmed 1045696512 bytes on /data

I/fstrim ( 172): Invoking FITRIM ioctl on /persist

I/fstrim ( 172): Trimmed 0 bytes on /persist

I/fstrim ( 172): Finished fstrim work.

Nexus 7 (2012)

┌─[brianklug@MBP] - [~/Downloads/APKs] - [Mon Jul 29, 03:46]

└─[$] <> ./adb logcat -d | grep -i fstrim

I/fstrim ( 122): Starting fstrim work...

I/fstrim ( 122): Invoking FITRIM ioctl on /cache

I/fstrim ( 122): Trimmed 122961920 bytes on /cache

I/fstrim ( 122): Invoking FITRIM ioctl on /data

I/fstrim ( 122): Trimmed 1087574016 bytes on /data

E/fstrim ( 122): Cannot stat mount point /radio

I/fstrim ( 122): Finished fstrim work.

I/fstrim ( 122): Starting fstrim work...

I/fstrim ( 122): Invoking FITRIM ioctl on /cache

I/fstrim ( 122): Trimmed 118923264 bytes on /cache

I/fstrim ( 122): Invoking FITRIM ioctl on /data

I/fstrim ( 122): Trimmed 782077952 bytes on /data

E/fstrim ( 122): Cannot stat mount point /radio

I/fstrim ( 122): Finished fstrim work.

Nexus 4

┌─[brianklug@MBP] - [~/Downloads/APKs] - [Mon Jul 29, 03:47]

└─[$] <> ./adb logcat -d | grep -i fstrim

- waiting for device -

I/fstrim ( 169): Starting fstrim work...

I/fstrim ( 169): Invoking FITRIM ioctl on /cache

I/fstrim ( 169): Trimmed 115343360 bytes on /cache

I/fstrim ( 169): Invoking FITRIM ioctl on /data

I/fstrim ( 169): Trimmed 888254464 bytes on /data

I/fstrim ( 169): Invoking FITRIM ioctl on /persist

I/fstrim ( 169): Trimmed 0 bytes on /persist

I/fstrim ( 169): Finished fstrim work.

I/fstrim ( 169): Starting fstrim work...

I/fstrim ( 169): Invoking FITRIM ioctl on /cache

I/fstrim ( 169): Trimmed 113246208 bytes on /cache

I/fstrim ( 169): Invoking FITRIM ioctl on /data

I/fstrim ( 169): Trimmed 1431195648 bytes on /data

I/fstrim ( 169): Invoking FITRIM ioctl on /persist

I/fstrim ( 169): Trimmed 0 bytes on /persist

I/fstrim ( 169): Finished fstrim work.

Users who have been experiencing slow I/O performance should see an improvement after getting the Android 4.3 update and letting fstrim run in the background a few times. Anand (the resident king of SSD and TRIM) is running some tests to investigate how much I/O performance can vary after an fstrim run.

My 16 GB Nexus 7, picked up on launch day last year, was slowly getting more and more frustrating to use. It hadn't hit the point many people had described in terms of complete unusability, but it certainly was worse than when I had first taken it out of the box... now, two days after updating to 4.3, the thing is as fast as it ever was.

I'm sort of confused why they hadn't added this to the operating system ages ago, but it's great to see it here now, and it's great to see the huge improvements!Reply

TRIM support was ostensibly added to Nexus 7 versions of Android back in 4.1.2, and while it made a difference, performance is still very much sub-optimal. The 4.3 update isn't going to change your current Nexus 7's performance.Reply

The vast majority of comments and Brian's testing above say the exact opposite: that the 4.3 update does indeed convert an unusably slow tablet into an extremely fast one. A D6A also says, it's likely that fstrim as a command was included in the code for 4.1.2, but it wasn't active. I don't think the criteria for activation (80%+, hour-plus deadtime) is aggressive enough and I would rather it attempt an fstrim on upgrade - like Android says, "Upgrading apps ..." - but that it's active rather than just present is a good step in the right direction.Reply

If you look at a pre-4.3 nexus device (perhaps 4.1.2 through 4.2.2), you'll notice that the writeable filesystems (i.e. /data and /cache) are mounted with the "discard" option. This means that the storage is trimmed after EVERY file delete operation. This prevents performance degradation over the long term, but the trade-off is that trimming on-the-fly can effect responsiveness.

4.3 no longer mounts filesystems with "discard" and instead runs TRIM on a schedule when the device is not being used. This has the benefit of preventing performance degradation over the long term, as well as not impacting responsiveness when the device is in use.

I suppose you could still run into temporary problems with this strategy if you were to fill up the entire filesystem with files followed by deleting them, all within a 24 hour period, before the storage has a chance to be trimmed. However, this is an unlikely scenario.Reply

Go to apps, and find the google services framework service. stop the service and wipe the data. Go back to about this tablet and try to upgrade (it should read last upgrade sometime in 1969). It may take 2 or 3 tries but eventually you will upgradeReply