Document directory
- 1. opengles trace
- 2. adrenoprofiler (v3.0.1)
- Lab
The latest Android ADT version contains the opengles trace option. Qualcomm provides an Adreno GPU performance analysis tool that can directly analyze the performance of opengles applications on Android/PC.
1. opengles trace1.1 version requirements
Android ADT: adt-bundle-windows-x86-20130219
2) Android ndk: android-ndk-r8d: r8d corrected the problem of ndk incremental compilation.
3)> = Android 4.1 (API Level 17)
1.2 generate a gltrace File
Window/show view/other/Open opengles trace view and click to enter.
For example, click the V-type button:
Configure gltrace, associate activity, and set the directory for storing gltrace files:
Gltrace progress dialog box:
1.3 analyze the effect of opening the trace view in the gltrace file. For example, we have tested the sanangeles example program that comes with ndk:
Refer URL: http://developer.android.com/tools/help/gltracer.html
2. adrenoprofiler (v3.0.1)
Refer URL: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources
Under the tools directory.
Lab
See the help documentation for specific software usage,
1. Open the application developed by opengles on the mobile phone
2. Open the software and click Connect.
3. Create a New Grapher page and double-click the view in the tree list on the right.EGL/FPSAndGPU General/busy
Test:
Data volume:
03-01 15:46:29. 482: I/VBO (10518): Position size = 1458000
03-01 15:46:29. 482: I/VBO (10518): normal size = 1458000
03-01 15:46:29. 482: I/VBO (10518): texture size = 972000
The vertex array and VBO can be significantly different when the vertex, normal, and texture data volume are about 1 MB.
For example, if you use VBO for rendering, the FPS is around 50, the GPU busy is around 100%, the FPS is around 30 when you switch to the vertex array, and the GPU busy is around 80%.