4 Display benchmarking
Vectornaut edited this page 2024-09-02 23:01:26 +00:00
This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

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 Browser VRAM 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% 89 W
e80adf8 Correct hit detection 5060% 1530% 50% 9 W Texture pipe and efficiency arbiter are more like 4560%
6db9f5b Only draw the top few fragments 5565% 1530% 5060% 9 W
6db9 variant LAYER_MAX = 8 3550% 1525% 3845% 9 W
a4236a3 Dim sphere interiors 5565% 1525% 5060% 94 MiB 10 W