Check small-write response before a remote coding interview

Does your laptop pause when saving code, switching projects, or opening lots of small files? Before a remote coding interview, check whether storage performance may be part of the problem. A short test can give you a useful baseline, but it cannot predict how every code editor or development tool will behave.

The Storage Test checks disk speed for large files and small writes, then gives a score out of 100. Run it before the interview, when you can close other work and repeat the test under similar conditions.

Test small-write response

1. Open the Storage Test on the computer you plan to use for the interview. Keep the test in the foreground and close files you do not need.
2. Start the test using its on-screen control. Let it finish without switching tabs or starting other tasks.
3. Note the small-write result and the overall score. If the test also shows large-file speed, note that separately so you can compare the two types of work.
4. Wait a minute, then run the test again under the same conditions. Similar results are more useful than a single run. If you use an external drive, test it separately from the internal drive.

Do not run the test during an interview or while you are saving important work. A storage benchmark makes temporary test data, and a busy computer can affect its result. Browser storage tests can also vary between runs, so use the number as a clue rather than a guarantee. Why storage benchmarks vary between browser runs explains some of the reasons.

What the result means

The result is similar each time

A repeatable result gives you a reasonable baseline for this computer, browser, and current workload. It does not mean every project will save at that rate, but it makes a one-off slowdown less likely to be normal behavior. If your coding tools are working smoothly, there may be nothing to fix.

Small writes are weak, but large-file speed is stronger

That pattern can point to work involving lots of small files rather than one large file. Code projects often contain many source files, configuration files, and dependencies, so small-write performance may be more relevant than a large-file result alone. It still does not prove the drive is failing. Available space, background activity, and the browser test itself can all affect the numbers.

Both types of result are low

A low result across the test may reflect a busy computer, a slower drive, a connection limit on an external device, or a test run affected by power-saving behavior. Compare runs on the same computer before drawing conclusions. A browser test does not identify the exact cause or diagnose drive health.

The results change a lot between runs

Another task may be using the drive, such as a file sync, software update, backup, or antivirus scan. The computer may also be warm or switching power modes. Wait for background work to finish, then repeat the test. A large difference is a reason to investigate the conditions, not proof that the drive is damaged.

How to improve the test and your setup

1. Wait for background work to finish. Pause a large file transfer or cloud sync only if it is safe to do so, and wait for updates to complete. Avoid stopping security checks or interrupting an update just to improve a benchmark.
2. Close apps that are using the drive. Close large projects, video editors, and other programs you do not need. On Windows 11, use Settings › System › Storage to review storage use. On macOS, open System Settings › General › Storage to check available space.
3. Keep the computer on a steady power setting. On a Windows 11 laptop, check Settings › System › Power & battery and avoid running the test in battery saver mode. On a Mac laptop, check System Settings › Battery. If practical, connect the charger and repeat the test.
4. Reconnect an external drive directly. If you are testing a USB drive, connect it to the computer rather than through a hub, and use the same port for each run. A cable, hub, or port can limit the drive's performance.
5. Restart and retest if performance remains inconsistent. A restart can clear stuck background activity. After signing in, wait for startup tasks to settle, then run the test again before opening your interview tools.

When the drive may need attention

One low browser score is not enough to call a drive faulty. Take the issue more seriously if normal tasks also pause, files take unusually long to save, or the computer reports read or write errors. Back up important files before troubleshooting further. If you hear unusual clicking from a hard drive, see repeated errors, or the drive disconnects, stop stressing it and get help from the device maker or a repair professional.

The Storage Test checks performance using temporary browser data. It does not inspect your interview files, measure every storage feature, or confirm the drive's remaining lifespan.