For editors and creators
An export is a marathon. The spec sheet timed a sprint.
Rendering and exporting load every core for minutes. SystemCheck measures what your machine holds across that time, and how fast it moves memory while it does.
What the report tells you
Three figures, each with its reading.
All-core throughput
ops/s
One worker per logical core, held for the length of the run. The peak is the spec sheet; the last fifth is your export.
Memory bandwidth
GB/s
From one thread and from all of them, plus the round trip to memory. Large timelines and raw photos live and die on this figure.
Consistency
%
How steady the throughput was window to window. A machine that averages well but stutters produces exports that take longer than the average says.
The diagnosis
The shape of the curve, read for your case.
01Held
Throughput stayed within a few percent of its peak for the whole run. The cooling is adequate for sustained work; upgrade for speed, not for stability.
02A single step down
A power limit. On a desktop this is often a motherboard default that can be raised; on a laptop it is the design.
03A steady slide
Cooling falls behind over the export's length. The last minute of a render runs on a slower machine than the first.
Every class comes with a stated confidence and the measurement’s own noise floor. How the shape is read
Where a browser stops
What it cannot tell you.
- No codec or GPU-encoder figure: the GPU stage is a raster and path-tracing load, not a hardware encoder test.
- No storage figure: no browser API measures a drive honestly, so scratch-disk speed is not attempted.
- No memory size: the browser reports bandwidth and latency, not how much is installed.
Which run
Deep, 8 minutes.
An export runs for minutes, so the settled level matters more than the peak. The deep run measures it as the median of three windows and states the spread.
Both kinds are free. The choice is on the set-up screen.
Questions
Asked in these words.
- Why does my export slow down partway through?
- The machine reached a sustained limit, thermal or power, and settled at a lower level than it started at. The test's curve shows when that happened and which kind of limit it was. If the curve is noisy rather than shaped, something else is competing for the cores during the export.
- Is memory bandwidth important for editing?
- Yes, for anything that streams large frames or raw files. The memory stage reports bandwidth from one thread and from all threads, and the latency to memory and to cache, so a slow or single-channel memory configuration shows up.
- Can this test my GPU encoder?
- No. The GPU stages load the raster pipeline and a path tracer, which tells you whether the card holds its performance under sustained load. Encoder throughput needs the editing application's own benchmark.