[Asus Transformer TF700] BarryH_GEG:
Here’s a description of the various data storage functions in Android as published by Google. Of the six, the only one that the tweaks being discussed apply to is SQLite. And those tweaks actually degrade reads pretty significantly and impact macros which are inherent to the other five data storage functions. The “6,000” score on Quadrant some have reported is based solely on improved SQLite reads and writes at the expense of the Quadrant read test. This shows up clearly in AndroBench as discussed in earlier posts. SQLite processes are contained 100% within a single app; it has nothing to do with the OS, general reads/writes, and anything shared between multiple apps or a single app and the OS. That’s why AndroBench and RL Benchmark show reduced performance in other key areas when the SQLite settings have been amped. So a great Quadrant IO score (a pretty weak IO test) isn’t reflecting the general performance of the TF700’s IO. So there's no question the tweaks are improving "in app" performance and SQLite-specific benchmarks but the other core IO issues the TF700 suffers from, especially disk reads and writes, are unchanged or worse because of them. And that's because s/w can't overcome inherent h/w limitations. As it stands, a TF700 writing multiple files simultaneously is 90% slower (12 MB/s vs. 0.19 MB/s) than an SGS3, One X, or Note because Asus' NAND implementation drops to random under stress. And nothing being discussed here has altered that.

Using the Internal Storage

You can save files directly on the device's internal storage. By default, files saved to the internal storage are private to your application and other applications cannot access them (nor can the user). When the user uninstalls your application, these files are removed.

Using the External Storage

Every Android-compatible device supports a shared "external storage" that you can use to save files. This can be a removable storage media (such as an SD card) or an internal (non-removable) storage. Files saved to the external storage are world-readable and can be modified by the user when they enable USB mass storage to transfer files on a computer.

Accessing files on external storage

If you're using API Level 8 or greater, use getExternalFilesDir() to open a File that represents the external storage directory where you should save your files. This method takes a type parameter that specifies the type of subdirectory you want, such as DIRECTORY_MUSIC and DIRECTORY_RINGTONES (pass null to receive the root of your application's file directory). This method will create the appropriate directory if necessary. By specifying the type of directory, you ensure that the Android's media scanner will properly categorize your files in the system (for example, ringtones are identified as ringtones and not music). If the user uninstalls your application, this directory and all its contents will be deleted.

Saving files that should be shared

If you want to save files that are not specific to your application and that should not be deleted when your application is uninstalled, save them to one of the public directories on the external storage. These directories lay at the root of the external storage, such as Music/, Pictures/, Ringtones/, and others.

Saving cache files

If you're using API Level 8 or greater, use getExternalCacheDir() to open a File that represents the external storage directory where you should save cache files. If the user uninstalls your application, these files will be automatically deleted. However, during the life of your application, you should manage these cache files and remove those that aren't needed in order to preserve file space.

Using Databases

Android provides full support for SQLite databases. Any databases you create will be accessible by name to any class in the application, but not outside the application.The recommended method to create a new SQLite database is to create a subclass of SQLiteOpenHelper and override the onCreate() method, in which you can execute a SQLite command to create tables in the database.

http://developer.android.com/guide/topics/data/data-storage.html

To show you what Zeus' impact is, here's a comparison to a Note and TF300 on JB. Red is perecent slower than the Note, green faster. After tweaking SQLite, the remainder of the TF700's IO scores remain significantly below that of the Note (or SGS3 or One X) and some are worse than stock. If you use the TF300 on JB as a proxy for how the TF700 would perform after the update the column on the far right shows the difference between the two.