To benchmark a PC, use the Benchmark and Diagnostics tab in S.A.K. Utility: open the Benchmarks sub-tab and click Run CPU Benchmark, Run Disk Benchmark, or Run Memory Benchmark. Each one gives you measurements and a score, where 1000 matches a known reference part.
When to use this
Use this to see whether a PC is performing as it should, to compare before and after an upgrade or repair, or to compare two machines.
What you need
- For the disk test, at least 1 GB free on the drive you test.
- For the disk test, a filled Drive: list. Click Scan Hardware on the Diagnostics sub-tab first.
- No internet connection.
- Usually no administrator rights. On the Windows drive the disk test uses your temp folder. On any other drive it uses the top folder, which Windows may only let administrators write to. If the test cannot start there, click Run as Admin and try again.
Steps
Close other programs, so they do not skew the numbers.
Open the Benchmark and Diagnostics tab.
Click the Diagnostics sub-tab.
Click Scan Hardware, and wait for it to finish. This fills the drive list.
Click the Benchmarks sub-tab.
One test runs at a time Click Run CPU Benchmark, and wait for it to finish.
In Disk I/O Benchmark, choose a drive under Drive:.
Click Run Disk Benchmark, and wait for it to finish. This takes a few minutes, and longer on a slow drive.
Click Run Memory Benchmark, and wait for it to finish.
Read the scores.
A score of 1000 matches the reference part named on the bar
To stop a test early, click Stop Benchmark.
What the scores mean
Each score compares this PC with one reference part. A score of 1000 matches it, and higher is faster.
- CPU: an Intel i5-12400. The bar shows the Multi-Thread score, which uses all cores. Single-Thread matters more for everyday programs.
- Disk: a Samsung 980 PRO SSD. A hard drive will score far lower, and that is normal.
- Memory: DDR4-3200 in dual channel.
How it works
- CPU: times four jobs: finding prime numbers, multiplying matrices, compressing data, and an encryption-style workload. It runs them on one thread, then on all of them, and works out how well the speed scales.
- Disk: writes a temporary 1 GB file to the drive, in your temp folder on the Windows drive and in the top folder on any other, bypassing Windows' file cache so it measures the drive itself. It then measures sequential speed over three passes, random small-file speed, and response time. It deletes the file when it finishes.
- Memory: measures read, write, and copy speed, the delay of random access, and how quickly memory can be set aside and freed.
Good to know
- The disk test writes real data: it writes at least 1 GB to the drive, which adds a small amount of wear to an SSD.
- The QD32 row: Random 4K QD32 (serialized QD1) sends one request at a time, as its label says. It is not a true queue depth of 32, so do not compare it with QD32 figures from other tools.
- The AES figure: the label says AES (S-box proxy) because it is a simplified workload, not real AES encryption. Do not compare it with other tools' AES results.
- Leftover file: if the app is closed abruptly during a disk test, delete the leftover
sak_disk_benchmark_file from the same place. - Saving results: to keep the numbers, export a Scan Report.