Currently development is paused - anyone interested in the source code write me a pm.
This app is aiming to give you better numbers for comparing different filesystems used in various lagfixes. It should also work for different phones, so that we can compare performance between them.
Currently this is a betaversion, so just try it out if you have a backup of your system. Even if nothing should happen to your system, i cannot guarantee for it![Wink ;) ;)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
PLEASE UNINSTALL PREVIOUS VERSIONS BEFORE TRYING A NEW ONE
Usage: Run the app, change the number of iterations in the options menu, and run Benchmark Filesystem. View your Results with "Last Benchmark Summary".
Reading the detailes values: Example: File writes 10k: 5378(53) kB/s
- The name describes the Test - here writing Files with 10kBytes size
- first number - here 5378 - is the mean value result - in this case the write speed in kBytes per second
- number in brackets: the approximate error (+-) of the mean value calculated.
The first test after a fresh installation can get somewhat faked numbers, repeat it at least two times to make sure to have reproducable values. If one value has a very large error compared to the others the reason could be another app doing something - just repeat the benchmark to see if its real.
Changelog 0.8:
- Refined Stress test and details
- FAQ added
- Logfile can now be copied (Longpress)
- Logfile structure changed for better overview
Changelog 0.7:
- Comparison bar chart added
- More detailed overall Score
- renamed it for broader future audience
- new icon set
- Minimum iterations is now 4
- the best and worst iteration are not taken for calculations - prevent statistical outliners
- Logfile lies now under TAPBenchmark
- Last benchmark numbers can be copied for fast pasting into this forum (Longpress)
Changelog 0.6:
- Additional Stresstest (Parallel read/write)
- Overall Benchmark Score introduced (has to be refined in future)
- Time for a Single Test can be changed to increase accuracy (maybe)
- Free space can be checked to ensure there is enough (no check before start yet)
- Write and Read test refined (data is now written/read to/from different files)
- Rewritten to be Android style (back-button working now as it should for example ...)
Changelog 0.5:
- Tests calculate readable values (Writes/s or kByte/s)
- Number of iterations can be changed (between 2 and 20) - standard is now 10
- Number of Repetitions per Test is automatically ajusted in the beginning so that each iteration takes approx. 1s - 7 tests with 10 iterations takes always approx 70s
- File read/write overhead is calculated: This is done by compare read/write speed of the 10k and 1M Tests under the assumption that the 1M tests give approx. the raw I/O speed. The number can be interpreted as additional time needed to read/write a file regardless of the size, which has to be added to the time it takes to read/write the file data itself.
- Display will stay on during the benchmark.
- sdcard test has been disabled- lets concentrate on /data first.
Reporting bugs and your Benchmark numbers is very welcome, i will include the numbers into the program for comparison. I will try to improve the tests to be as meaningful as possible, so post any ideas you have for improving it.
This app is aiming to give you better numbers for comparing different filesystems used in various lagfixes. It should also work for different phones, so that we can compare performance between them.
Currently this is a betaversion, so just try it out if you have a backup of your system. Even if nothing should happen to your system, i cannot guarantee for it
PLEASE UNINSTALL PREVIOUS VERSIONS BEFORE TRYING A NEW ONE
Usage: Run the app, change the number of iterations in the options menu, and run Benchmark Filesystem. View your Results with "Last Benchmark Summary".
Reading the detailes values: Example: File writes 10k: 5378(53) kB/s
- The name describes the Test - here writing Files with 10kBytes size
- first number - here 5378 - is the mean value result - in this case the write speed in kBytes per second
- number in brackets: the approximate error (+-) of the mean value calculated.
The first test after a fresh installation can get somewhat faked numbers, repeat it at least two times to make sure to have reproducable values. If one value has a very large error compared to the others the reason could be another app doing something - just repeat the benchmark to see if its real.
Changelog 0.8:
- Refined Stress test and details
- FAQ added
- Logfile can now be copied (Longpress)
- Logfile structure changed for better overview
Changelog 0.7:
- Comparison bar chart added
- More detailed overall Score
- renamed it for broader future audience
- new icon set
- Minimum iterations is now 4
- the best and worst iteration are not taken for calculations - prevent statistical outliners
- Logfile lies now under TAPBenchmark
- Last benchmark numbers can be copied for fast pasting into this forum (Longpress)
Changelog 0.6:
- Additional Stresstest (Parallel read/write)
- Overall Benchmark Score introduced (has to be refined in future)
- Time for a Single Test can be changed to increase accuracy (maybe)
- Free space can be checked to ensure there is enough (no check before start yet)
- Write and Read test refined (data is now written/read to/from different files)
- Rewritten to be Android style (back-button working now as it should for example ...)
Changelog 0.5:
- Tests calculate readable values (Writes/s or kByte/s)
- Number of iterations can be changed (between 2 and 20) - standard is now 10
- Number of Repetitions per Test is automatically ajusted in the beginning so that each iteration takes approx. 1s - 7 tests with 10 iterations takes always approx 70s
- File read/write overhead is calculated: This is done by compare read/write speed of the 10k and 1M Tests under the assumption that the 1M tests give approx. the raw I/O speed. The number can be interpreted as additional time needed to read/write a file regardless of the size, which has to be added to the time it takes to read/write the file data itself.
- Display will stay on during the benchmark.
- sdcard test has been disabled- lets concentrate on /data first.
Reporting bugs and your Benchmark numbers is very welcome, i will include the numbers into the program for comparison. I will try to improve the tests to be as meaningful as possible, so post any ideas you have for improving it.
Attachments
Last edited: