Start recording display benchmark results

Vectornaut 2024-09-02 22:46:49 +00:00
parent 6ebbc6065e
commit efae41f509

14
Display-benchmarking.md Normal file

@ -0,0 +1,14 @@
To make sure the display stays responsive, we've been tracking how changes affect its performance.
## Procedure
Build with `--release`. Test on Chromium with VSCodium, gedit, and the AMDGPU_TOP GUI running, and all other programs closed. In case it matters, keep the display prototype fully visible on the right half of the screen, with the AMDGPU_TOP plots visible on the left half. Start the turntable and then monitor AMDGPU_TOP stats for a minute or so.
## Results
Commit | Description | Graphics pipe | Browser CPU | Browser GFX | GPU power | Comments
---|---|---|---|---|---|---
`4afc820` | Sort fragments while shading | 5060% | 1530% | 50% | 9 W
`4afc` variant | `SPHERE_MAX_INTERNAL = 12` | 8090% | 1520% | 8090% | 27 W
`4afc` variant | `SPHERE_MAX_INTERNAL = 4` | 4050% | 1520% | 3540%
`e80adf8` | Correct hit detection | 5060% | 1530% | 50% | 9 W | *Texture pipe* and *efficiency arbiter* are more like 4560%