CamMicGo
Documentation de ce test
WebGPU

WebGPU sur cet appareil

WebGPU ne s’installe généralement pas séparément. Sa disponibilité dépend du navigateur, du système, du pilote graphique et du GPU.

Moteur de stress CamMicGo
WebGL 2 pour conserver une comparaison inter-navigateurs
Pourquoi WebGPU peut être intéressant

WebGPU est le successeur moderne de WebGL. Il correspond mieux aux API GPU modernes, permet des calculs généraux sur le GPU et peut réduire la charge CPU dans les applications bien conçues. Il n’est pas automatiquement plus rapide dans tous les tests.

GPU Stress Test

Load your graphics hardware from the browser and watch frame rate, frame pacing, artifacts and device stability.

This is a stability and behavior test, not a benchmark or GPU ranking.

Graphics hardware

Detecting...

Detected by browser
Unavailable · WebGPUUnavailable · WebGL 2Unavailable · WebGL 1
Rendering engine

Selected engine: WebGL 2. Results from different APIs should not be treated as identical benchmark scores.

Your device can get hot during this test

GPU load can increase temperature, fan speed and battery drain. Phones and thin laptops may reduce performance by design.

FPSLevel 1/100sWebGL 2
The stress scene appears here once you start.
Current FPS
Average FPS
1% low
Dropped samples
First → last

FPS versus display refresh

Dynamic scale: small FPS changes are magnified so a real decline is easy to see.

Display: 60 Hz
686052Display 60 HzDrop threshold 53 FPS0s10s
Blue: measured FPSDashed blue: display refreshAmber: automatic drop thresholdRed dots: samples below threshold
Threshold, not a score

If the Ramp stops at level 4, it means this scene stopped matching the display refresh there. It does not mean your GPU scored 4 out of 10.

Why the line may stay flat

At 60 Hz, the browser is normally synchronized near 60 FPS until the workload finally becomes too heavy. The zoomed scale makes the first decline much easier to spot.

API matters

WebGPU and WebGL 2 use different browser and driver paths. Compare repeat runs within the same API rather than treating the two as interchangeable benchmarks.