GPU browser render test v1 (gpu-bench@1, WebGPU) and load check

How to use

1. Use a desktop browser with WebGPU (recent Chrome/Edge). Keep this tab in front; a hidden tab cancels the test.
2. Press start. A 0.5 s warm-up and a 2 s window run 5 times; the median is the result and the spread is shown.
3. The score counts work completed by the GPU: GPU timestamps if the browser exposes them, otherwise the CPU-side time from submission to completion. Frames shown on screen (rAF) are never used.
4. Pick “GPU to use”: high performance (default) or low power. WebGPU cannot choose a GPU by name; this is only a hint, and the GPU the browser reports is shown before and after the run and saved with the result.

Benchmarking a second GPU on Windows 11

1. Open Settings → System → Display → Graphics.
2. Add your browser (Brave / Chrome / Edge) as an app, open its Options, and choose “Specific GPU” (pick the GPU) or High performance. Save.
3. Fully restart the browser, open this page again and check the GPU shown under “GPU used for this test”.
4. Run the test. Results are grouped per GPU in your history, so the two GPUs are compared side by side instead of mixed.

On laptops, “high performance” usually selects the discrete GPU and “low power” the integrated one. If the browser hides the GPU name, you can label the run with one of your My PC GPUs; it is marked as self-reported. Per-GPU testing by name is planned in PartsLife (the Windows app).

Worked example

Example (illustrative): 640 units/s with CV 2%, timing “CPU-side submit-to-completion”, adapter “nvidia / ampere” as reported by the browser. One unit = 16,384 instanced cubes at 1280×720 plus a 65,536-thread integer compute pass.

Limits

• The GPU name is what the browser reports (reference only); it may be hidden, coarsened, or not the GPU actually used (e.g. hybrid laptops).
• This is a browser/WebGPU test. It is not game FPS and is not combined with the CPU test into one score.
• Timing methods differ (GPU timestamps vs CPU-side) and are recorded; compare only the same timing and resolution. Timestamps may be coarsened by the browser.
• The load check ends with “no computation mismatch was detected within the time” at best; it is not a stability certificate. It stops on the stop button, an independent timer, a hidden page, or device loss.
• Safety: heavy GPU load heats the PC and drains laptop batteries. Stop if it gets hot or noisy. A driver may reset the GPU under load; save your work first.

Your inputs and results stay in this browser. Nothing is sent to a server.