XDA member supercurio has been working on the Ext4 file system for a little while now, and you may remember that there are results out of that already for the Nexus S with this improved kernel. But what is this about? In essence, the use of a safe mount option would allow the device to perform certain internal tasks better without compromising data integrity or file system integrity if the system was to fail for some reason (crash).
There has been some benchmarking done for his work and it seems to get a significant boost after this option is enabled. The dev also states that the benchmark used (Quadrant), while not really crucial, it would yield interesting information for comparison purposes. The whole discussion is rather technical, but we thought it was still worth pointing it out as a reference. After all, some people may wonder why their Nexus S is running faster all of the sudden
As I spend some time on studying Ext4 for the Galaxy S devices, working on Voodoo lagfix, and based on what I saw in mount logs it’s possible that the performances could be increased without altering data integrity nor filesystem integrity in case of crash.
On /data, noauto_da_alloc is not used.
This option activates a sort of Ext3 emulation mode, which force sync on write close without sync.
It also comes with a speed penalty for SQLite writes, and is unneccessary when hardware barriers are enabled.
Barriers allow usage of delayed allocations without risk. Delayed allocations are the key to performance for modern filesystems.
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer._________
Want something on the XDA Portal? Send us a tip! -- Join us for xda:devcon 2014!