Tweet
We are pleased to announce that PerformanceTest Mobile 2.0 for Android 3.0 (Honeycomb) and later (API 11+) has now entered beta and is available for download and testing.
Current Beta Version
Beta 1
Download Link
https://play.google.com/store/apps/details?id=com.passmark.pt_mobile
What's New in Version 2.0
Keep any comments, bugs, suggestions, questions in this thread. For bugs, please also let us know the device/model being used. You can also send email in if preferred.
Current Beta Version
Beta 1
Download Link
https://play.google.com/store/apps/details?id=com.passmark.pt_mobile
What's New in Version 2.0
- CPU, Disk and Memory tests are now using native code. Individual test results (not the calculated Marks) should now be more comparable to their PerformanceTest desktop counterpart. See known issues section below.
- New Single threaded CPU test.
- Completely new Memory Tests. Now including: Database Operations, Memory Read Cached, Memory Read Un-cached, Memory Write, Memory Latency, and Memory Threaded Test.
- Re-written disk tests. Tests will be performed without cache where available.
- New 3D OpenGL ES test created using Unity.
- Improved system information. Including Battery information and Screen dimensions.
- CPU Encryption tests now uses cryptopp library.
- Updated bouncing balls 3D test.
- New baseline management feature, including ability to save to device, search our database, and compare results within the application itself.
- With new tests being added and old test updated. The results from V1 may not be comparable with V2.
- To keep the size of the application reasonable, we no longer support MIPS architecture.
- Some lower memory devices may not be able to run or run but return no results on the OpenGL ES Test using Unity. Android will start closing programs that use too much memory which might cause the program to crash/restart without notice.
- Disk Internal/External Read tests may fail when running the complete benchmark suite with the error "Failed to Create Test File". However, the test might actually be okay when run manually.
- The Disk test will now commence without using cache (if possible), as such, the disk tests read and write speeds will be lower than V1. If cache is in use, PerformanceTest will note it and you may see similar results as in V1.
Keep any comments, bugs, suggestions, questions in this thread. For bugs, please also let us know the device/model being used. You can also send email in if preferred.
Comment