Why shader workloads differ from video playback
Learn why a browser Graphics Test stresses shaders differently from video playback, what its score measures, and how to compare both workloads fairly.
Your video plays smoothly, but a graphics benchmark gives you a score you did not expect. Or a browser animation stutters even though movies look fine. These results can seem contradictory because shader tests and video playback ask different parts of the graphics system to do different work.
The Graphics Test measures shading power and fill rate at 1080p. Here is what that workload checks, why it is not a video playback test, and how to interpret the two experiences together.
Run the Graphics Test
- Open the Graphics Test on the computer you want to check.
- Start the test using the on-screen control. Let it finish, and note the score out of 100 and whether the animation appears smooth.
- Close other graphics-heavy tabs or apps, then run the test again if you want to check whether background activity affected the result.
- Separately, play a video you normally watch. Note its resolution and whether it stutters, drops frames, or plays smoothly. Do not treat this as a direct score comparison.
The test runs on your device. Its score is useful for comparing runs on the same computer under similar conditions, but it is not a universal rating of every graphics task.
What the results mean
The Graphics Test scores well and looks smooth
The browser completed this shader and pixel workload effectively at 1080p. That is a good sign for similar browser graphics work, but it does not prove that every game, video format, or graphics application will perform equally well. Those may use different features or put different demands on the computer.
The Graphics Test score is low, but videos play smoothly
This can be normal. Video playback may use a dedicated video-decoding circuit that handles common compression formats efficiently, while the Graphics Test measures shader calculations and pixel output. A computer can be good at one task and less capable at the other.
The score is strong, but a video stutters
The video may be using a format the browser cannot decode efficiently, or it may be relying on the processor instead of a supported hardware decoder. The network, the video player, background tasks, or the display setup can also cause stutter. The Graphics Test score alone cannot identify which one is responsible.
The score changes between runs
Other apps may be using the graphics processor, or the computer may change its power and cooling behavior under load. Browser versions, graphics drivers, and the display resolution can also affect results. Compare runs in the same browser, with similar apps open and the same power conditions.
Compare the two workloads fairly
- Keep the conditions consistent. Use the same computer, browser, display, and power source for repeated Graphics Test runs. Close games, video editors, and other demanding apps first.
- Check the video details. Resolution and compression format matter. A high-resolution or high-bitrate video can be harder to play than a standard 1080p clip, even if both appear to be ordinary videos.
- Look for where the problem occurs. If one video stutters but other videos play well, suspect that video's format, player, or source before assuming the GPU is failing. If browser animations and multiple graphics apps also struggle, the graphics path deserves closer attention.
- Compare like with like. Use repeated Graphics Test runs to check browser graphics performance. Use actual playback to judge video playback. Neither result substitutes for the other.
Why shader workloads differ from video playback
A shader is a small program that calculates how graphics should look. A graphics test can run many shader calculations to create an image, then measure how quickly the computer shades and outputs pixels. Too many calculations or pixels for the graphics processor to handle can reduce the score or make the animation less smooth.
Video playback usually starts with compressed video data. Many graphics processors include specialized video-decoding hardware for common formats. When the browser, video format, and driver support that hardware, it can decode frames without asking the general-purpose shader units to do all the work. This is one reason a modest computer can play video smoothly while earning a lower score in a shader-focused test.
The paths are not completely separate. A browser may use the graphics processor to scale, compose, or display video frames, and some video effects can involve shader work. The processor and graphics processor also share memory or power limits on many computers. But playing a video does not normally reproduce the same repeated shading workload as a graphics test.
Video playback also depends on factors the Graphics Test does not measure, including the video's codec, the browser's decoder support, and the source's bitrate. A video that stutters is not by itself proof of a weak GPU, just as smooth playback does not prove strong shader performance.
Use the Graphics Test to check browser-based shading and fill rate, and use the video that matters to you to check playback. Both run in your browser, but they answer different questions.
