O teste em si, o relatório e o resto do site estão em inglês por enquanto.
Descubra por que seu PC fica lento.
Um teste de estresse gratuito no seu navegador. Ele mede o que seu PC sustenta sob carga e aponta a causa.
O diagnóstico
Não quanto ficou lento. Por quê. O formato da curva é o diagnóstico, e o relatório o interpreta.
Uma pontuação diz que a máquina ficou mais lenta. A curva por trás dela diz o que aconteceu. Três formatos importam, cada um com uma causa diferente.
A single step down
A power budget expiring. The machine held its boost for as long as it was allowed to, then dropped to the sustained limit in one move.
A steady slide
Cooling falling behind. Every second under load, a little more is lost, and it does not settle until the fan can keep pace.
A sawtooth
A machine cycling between the two: it cools, boosts, hits the limit, drops, and repeats.
Quatro etapas e então um nome para o que aconteceu. A máquina sustenta o que a ficha técnica prometeu? E se não, por quê?
Stage 1
Every core, for 60 seconds. The number that matters is the one it settles at.
Parallel Web Workers saturate every logical core and the main thread samples throughput four times a second. Peak arrives in the first second; the rate the machine holds once cooling becomes the limit is what gets reported.
Illustrative run. Your own cores draw their own.
Stage 2
One thread, then six. How much more the memory system gives when asked.
Workers stream 24 MiB arrays to measure bandwidth from one thread and then from all of them, and a pointer chase through a shuffled array measures how long a round trip to memory takes. A machine whose bandwidth barely scales with threads is telling you about its memory channels, not its cores.
One thread
Six threads
Illustrative figures. Not a measurement.
Stage 3
One fixed scene, the same on every card. Frame time, pacing, and how far it falls.
A lit 3D model renders at a fixed 1600 by 900 on a camera path that repeats every ten seconds, and every frame is timed until the graphics chip has finished it. Frames per second, how steadily they arrive, and how far the rate falls are reported. Stutter and slowness look different here, which is the point.
Illustrative frame rates. Not a measurement.
Stage 4
The same scene, soft edges and hard. What realistic shadows cost your card.
The Deep run draws one scene at 1600 by 900 with percentage-closer soft shadows and with plain hard shadows, switching every nine seconds, and times every frame. The gap is the share of frame rate soft shadows take. It is reported, never scored, and the same test runs on its own page.
Illustrative frame rates. Not a measurement.
Stage 5
Samples back to back, each one timed. So the cost of each sample is the measurement.
A WebGL2 path tracer runs samples back to back at a fixed 960 by 540, accumulating each into a float texture, and times every one until the graphics chip has finished it. Samples per second and delivery consistency are reported; a card that delivers unevenly is distinguishable from one that is merely slow.
Illustrative progress. Not a measurement.
Report
Not how much it slowed. Why. The shape of the curve is the diagnosis.
A plateau that steps down once is a power budget expiring. A steady slide is cooling falling behind. A sawtooth is a machine cycling between the two. The report reads the shape, states its confidence, and names the cause with the number to beat on the retest. The next run on the same machine is shown against this one.
Plateau, then a single step down.
Throughput held for 18 seconds, then fell in one transition and stayed there. One fall accounts for 98% of everything the run gave up.
Illustrative shape. Your run draws its own, and the report reads that one.
Os limites, ditos com clareza
O que um navegador não consegue ver.
Nenhuma página web consegue ler uma temperatura. Uma máquina limitada pela refrigeração ainda assim se revela, como queda, e a queda não precisa de sensor.
Formatos ilustrativos. Uma máquina mantém perto de 96% do pico; outra estabiliza em 64%.
A confiança de quem exige do hardware. Montadores, integradores, técnicos de reparo.
“I was about to buy a second-hand ThinkPad for 400 quid. Ran the test in the seller's kitchen, watched the CPU stage lose 38 percent in three minutes, and walked away. Best three minutes I spent that week.”
Marcus R. · Buying a used laptop“I hand out one link to clients now instead of a download. They run it, forward me the report, and I know before I drive over whether the cooling is the problem.”
Priya S. · System integrator“My frames were fine for ten minutes and then fell off a cliff every night. The graphics stage showed the same drop at the same point, and the report said thermal ceiling in plain words. New paste, problem gone.”
Devon L. · Gamer, fixed his FPS drops“Exports kept getting slower the longer I worked. I assumed it was the software. The memory stage showed the laptop was fine on mains and lost a third of its speed on battery. Now I edit plugged in.”
Ana M. · Video editor“It says up front what a browser cannot see, and then measures the rest properly. That honesty is why I trust the number it gives me over a spec sheet.”
Tom K. · Sceptical by trade“Forty refurbished desktops in an afternoon, one link each, same test on every machine. The three that graded D all had dust-packed fans. The report told me before the screwdriver did.”
Jordan P. · IT refurbisher“Watching ops per second sink live while the fans spun up taught me more about my machine than any single score ever did. The retest target told me exactly what to aim for after the fix.”
Sana D. · Curious about her own PC“New build, new cooler, and I wanted proof it was worth it. Before and after in two runs: decay went from 31 percent to 6. That is the number I put in the forum post.”
Leo V. · First-time PC builder“Twelve laptops in the classroom, three complaints a week that they were slow. Ran the test on all of them from the same link. Two were throttling badly, ten were fine. Two repairs instead of twelve.”
Ravi N. · School IT admin“I asked in a forum why my new PC felt slower than the reviews said. Someone sent this. Three minutes later I could see it was hitting a power limit under load, and I knew what to change in the BIOS.”
Emily W. · New PC underperforming“Average FPS looked great and the racing still felt wrong. The consistency figure caught frame pacing my overlay was hiding. Once I could see it, I could fix it.”
Chris B. · Sim racer“Customers say slow, I need a number. I run it in the browser while they watch, the report says what is happening in plain words, and the repair conversation is over in a minute.”
Nadia F. · Repair shop ownerCada peça, com suas especificações. E o que elas não contam.
1,737 processors and every graphics card we can source properly, with side-by-side comparisons. 218 carry a full sheet today; the rest say “not verified” rather than guess.
Artigos
Melhor conforme você lê. Guias e notas sobre medir com honestidade.
- Memory latency vs bandwidth: what a random-walk test showsBandwidth is how many bytes memory moves per second; latency is how long one dependent load waits. How SystemCheck measures each and what they cannot say.
- Single-thread vs all-thread memory bandwidthWhy SystemCheck measures memory bandwidth on one thread and then on several, what the ratio between the two shows, and what it cannot prove.
- What "not measured" means in your reportWhen a stage cannot run or its data cannot be trusted, SystemCheck says not measured and gives the reason instead of estimating a number.
- Reading the confidence interval on every figureEach headline figure in a SystemCheck report carries an interval: the spread inside that one run. How it is computed, what it covers and what it does not.