System information

Browser-reported capabilities Browser hints, not hardware detection

Browser-reported logical processors Not supplied

Browser-reported graphics Not disclosed by browser

Browser memory hint · not installed RAM Not supplied

These values are browser-provided hints, not a hardware inventory. The memory hint is neither installed RAM nor free memory: a device with 32 GiB installed can report a smaller value. Vigilum cannot determine your actual capacity from this hint; check your operating system for installed RAM. Privacy protections can also limit processor counts and mask graphics names. Compare runs in the same browser and configuration.

Know your workload.
See every measurement.

Choose your workload

Nothing runs until you press Start.

CPU

Render a fixed scene and measure tracing throughput.

Open CPU tests

GPU

Watch a live rendering workload and inspect frame timing.

Open GPU tests

RAM

Choose a memory budget and inspect verified coverage.

Open RAM tests

Combined

Run CPU, graphics, and memory workloads together.

Open combined stress

Before you start

Start small

Save other work. Begin with a bounded run and a modest memory budget.

Compare like for like

Keep workload versions, modes, backends, and settings consistent.

Understand the limits

Browser results do not measure temperature or certify hardware health. Read the safety guide.

Testing guide & measurement glossary

Understand the readings

CPU render time: Time to finish the fixed tracing workload after worker warm-up. The uncalibrated index is 1,000 divided by seconds; compare only matching workload versions and quality.
GPU frame timing: Recent browser presentation rate and frame intervals, not GPU utilization. GPU.js sphere intersections and Three.js raymarching are different workloads, not interchangeable scores.
Memory measurements: Bandwidth, access latency, and expected-value checks within the allocated memory. They do not test all physical RAM or certify hardware health.

Make runs comparable

Save other work, close busy applications, and keep this tab visible.
Use the same browser version, workload, backend, and settings when comparing runs.
Keep power settings consistent. Start with a short run and a modest memory budget.
Stop if the device becomes unstable. This page does not measure temperature or diagnose hardware faults.