Not measured means SystemCheck has no figure it can stand behind, so it prints none. Nothing is estimated in its place.
- Every not-measured line carries its reason: the browser could not run the stage, the stage was skipped, the tab was hidden, or the run predates the stage.
- A score part that did not count is left out of the score rather than credited or penalised.
- Some things are never measured by any browser: temperature, power draw, fan speed, memory capacity and graphics memory size.
Why a blank beats a guess
A benchmark that fills a missing figure with an estimate hands you a number that looks measured and is not. SystemCheck's rule is the opposite: a figure is printed only when the run produced it, and where it did not, the report says not measured and gives the reason. The same rule covers the hardware catalogue, where a specification that has not been verified shows as not verified rather than as a guessed value.
The common reasons, and what to do
Each of these is a reason the report can give:
- The GPU stage could not run on this browser. The browser did not offer the graphics interface the stage needs. Try a current version of Chrome, Edge or Firefox with hardware acceleration on.
- Path tracing was skipped, or could not complete on this browser. A shorter run can skip it; otherwise the browser stopped the stage before it finished.
- The memory stage predates the run, or could not complete. Older reports were made before the stage existed; a stage that could not start its workers stops rather than guessing.
- The browser did not report a steady frame clock. The screen check needs a regular frame timer, and without one the refresh rate is not printed.
- Soft shadows did not measure. The tab was hidden, the window lost focus for most of a pair of segments, or WebGL2 was missing.
- Worker threads could not start. The CPU figure was taken on one core, and the report labels it single-core so it is never set beside a multi-core figure as if the two were alike.
How a missing figure affects the score
The overall score is built from parts. A part whose stage did not measure does not count: it is shown as did not count in this run, and the remaining parts carry the score. Nothing is credited for a stage that did not run, and nothing is taken away for it either.
What is never measured
Some lines are blank on every run because no web page can read them. Browsers expose no temperature, power draw, fan speed, clock frequency, memory capacity or graphics memory size. SystemCheck infers behaviour from the work a machine completes over time, and leaves the sensor readings to native tools.
Terms used here
Questions
- Will running again fill in a not-measured figure?
- Often, if the reason was a hidden tab, a lost focus or a stage that stopped early. Keep the tab in front and the window focused for the whole run. If the reason was the browser itself, try a different current browser.
- Why does SystemCheck not show my CPU temperature?
- Browsers expose no temperature sensor to web pages, so no browser tool can read it. SystemCheck measures throughput over time instead and says so.