Test methodology
What does the Shader Pipeline Test measure?
It measures how efficiently the browser, graphics driver, and GPU render a fixed 3D scene using different WebGL vertex and fragment shader techniques.
Which shader techniques are tested?
The test covers cel shading, vertex lighting, fragment or pixel lighting, bump mapping, relief mapping, environment reflection, and Fresnel reflection and refraction.
How does the Shader Pipeline Test run?
During a measured run, each shader configuration renders 2,000 frames of the same animated 3D scene. The camera, object, and lighting change over time while the workload renders at a fixed internal resolution of 1920 x 1080.
How is the Shader Pipeline score calculated?
The test records the frame count and rendering duration for every shader configuration. Its result is based on the median rendering throughput across the configurations and the official test weight. Higher scores are better.
What affects the Shader Pipeline result?
Results can be affected by the GPU, browser WebGL implementation, graphics driver, power mode, temperature, and competing workloads. Comparisons should use the same test version and graphics profile.
Does it measure shader compilation speed?
No. Shader materials and assets are prepared before measurement. The test primarily measures sustained rendering performance, not isolated shader-compilation latency.
How to interpret the result
The result reflects sustained rendering throughput across the tested shader and material techniques in the fixed 3D scene.