The second curve is the result of the PVRTune testing while running the 3D Mark graphics program. The first curve is obtained using the PVRScopeStats API while running the 3D Mark graphics program.
I guess PVRTune somehow fixs the clock speed. Is there a way for me to set a fixed clock speed when I’m using PVRScope
Thanks for your message, and welcome to the PowerVR Developer Forum!
After speaking with the Tools Team I confirmed that PVRTune does not change the GPU clock speed when recording from a PowerVR device. The results you are obtaining with PVRScope are likely to be due to the frequency you are sampling (possibly each frame?) You could try getting results with a lower frequency rate, or applying some high-frequency filtering to the values.
As for the results on PVRTune, the tool has an option to smooth the plot of all GPU counters displayed, which produces the results similar to the ones you are obtaning:
I’m focus on GPU Clock Speed because the data I obtain with PVRScope shows more volatility than PVRTune. For example, GPU PowerVR Series8XEP, GE8320, Device 0/GPU memory write bytes per second, GPU PowerVR Series8XEP, GE8320, Device 0/Renderer active (%), GPU PowerVR Series8XEP, GE8320, Device 0/Shader/Shaded pixels per second …
Regarding the GPU clock speed GPU counter not showing any information, please make sure to:
Install PVRPerfServerDeveloper on the device you are taking recordings from.
If you have used more than one PVRTune version, then make sure that there is a match between the version installed in the device and the PVRTune version you are using to take any recordings.
Regarding data volatility, the Renderer Active GPU counter is a binary counter (it either has a value of 0% or 100%):
I can see in the file provided entries like “Renderer active: 77.362137%”, please for that GPU counter treat its value as value 0 → Renderer not active, value > 0 → Renderer active.
Also, for comparing the values from PVRTune and the values from PVRScope, are you exporting the values from PVRTune as a .csv? (using File -> Export -> Export raw data to .csv). In that case, there is a PVRTune issue which was reported on a different thread ( How to get Geometry active value from exported .csv file? - #9 by AlejandroC ) and was fixed internally. The fix will be included in the next PVRTune release (I can also provide an engineering drop if you need it).