From efae41f509d091a20fd424dc4ef188609f2e1282 Mon Sep 17 00:00:00 2001 From: Vectornaut Date: Mon, 2 Sep 2024 22:46:49 +0000 Subject: [PATCH] Start recording display benchmark results --- Display-benchmarking.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 Display-benchmarking.md diff --git a/Display-benchmarking.md b/Display-benchmarking.md new file mode 100644 index 0000000..71f2dcf --- /dev/null +++ b/Display-benchmarking.md @@ -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 | 50–60% | 15–30% | 50% | 9 W +`4afc` variant | `SPHERE_MAX_INTERNAL = 12` | 80–90% | 15–20% | 80–90% | 27 W +`4afc` variant | `SPHERE_MAX_INTERNAL = 4` | 40–50% | 15–20% | 35–40% +`e80adf8` | Correct hit detection | 50–60% | 15–30% | 50% | 9 W | *Texture pipe* and *efficiency arbiter* are more like 45–60% \ No newline at end of file