Reference/Glossary
Glossary. Every term in a report, explained.
88 CPU, GPU, thermal and benchmarking terms, defined. 37 name the metric SystemCheck measures for them; the rest say what a browser cannot read.
What the words in a benchmark report mean
This glossary defines the 88 terms used in a SystemCheck report and in the guides around it, grouped into 11 categories: CPU, GPU, Thermal, Benchmark, System, Network, Video, Display, Audio, Input, Storage. 37 are marked Measured, which means the report carries a figure for that term on your own machine. The other 51 give the context around those figures, including readings that no browser exposes, so you know what a sensor tool would add.
Each entry opens with a one-line definition, then explains the idea at more length and links to the terms it depends on. Browse by category, or use the A to Z index at the foot of the page. If a word in your report is unfamiliar, its entry says what the number describes and, just as plainly, what it does not.
The terms are worth most next to a result. Run the free browser test, which takes 3 minutes in its standard mode, and read the report with this page open: sustained clock, thermal decay and run-to-run variance mean more against your own curve than against a definition.
Good places to start
CPU
Clocks, cores, power limits, and the behaviour of a processor under sustained load.
GPU
Rendering work, frame delivery, memory, and the browser graphics backends SystemCheck runs on.
Thermal
Heat movement, cooling capacity, and the temperature effects that shape sustained performance.
Benchmark
How measurement is run, scored, compared, and kept honest across repeat runs.
System
Whole-machine behaviour: bottlenecks, bandwidth, power delivery, and result contamination.
Network
Delay, its variation and loss on a connection, and what a browser can and cannot time.
Video
Codecs and the hardware that decodes them, as the video decode test asks about them.
Display
Refresh, motion and colour: what a screen does, what its spec sheet means, and what a page can read.
Audio
Speaker layouts and wireless delay, checked by ear and by tapping along.
Input
Mice, controllers and the delay between a press and the screen.
Storage
Solid-state drive behaviour behind the speed and endurance figures on a spec sheet.
A to Z
Questions
That SystemCheck reports a figure for it from your own run. 37 of the 88 terms carry the label; the rest are defined for context and are not read by the test.
Because they explain the numbers the test does read. No browser can read a temperature, a fan speed or a wattage, but knowing what a temperature limit is helps you read a curve that falls away, and tells you what to check in a sensor tool.
Peak is the best a machine delivers for a short burst. Sustained is what it still delivers after minutes of load. SystemCheck measures the second because it is the one that decides how a long game, export or build feels.
In the report at the end of the free browser test. The standard run takes 3 minutes; the deep run takes 9 minutes and covers more stages.
Every figure on a definition is a design target. None of it is a measurement.
Nothing above describes how a machine behaves twenty minutes into a sustained workload, which is where two chips with nearly identical specifications routinely diverge. A boost clock is a ceiling the vendor permits, not a rate the chip sustains, and whether it holds depends on the cooling, the case, the power profile and the room. None of those appear on a specification sheet.
We deliberately do not reduce these figures to a single score. A composite invented from specifications would look authoritative and measure nothing, and choosing the weights would be choosing the winner.