Blog

What slow small-write performance means for daily use

Learn why slow small writes can make everyday tasks feel sluggish, how to check storage performance, and what the result can and cannot tell you.

Michael ReedHardware tests 5 min read

Your computer may copy a large video quickly but still feel slow when opening apps, saving documents, or installing updates. Those tasks often involve many small writes, which means saving lots of little changes rather than one large block of data.

The Storage Test checks large-file speed and small-write performance in your browser. Use it to see whether small writes look like a possible bottleneck, then compare the result with what you notice during ordinary tasks.

Check small-write performance

  1. Open the Storage Test on the computer you want to check.
  2. Let downloads, file copies, cloud sync, and other busy tasks finish. They can compete for storage and make a result harder to interpret.
  3. Run the test and look at the small-write result alongside the large-file result and the score out of 100.
  4. Repeat the test once under similar conditions if the result seems surprising. A large change between runs can point to background activity or normal test variation.
  5. Note what felt slow at the same time. For example, check whether saving a small document or opening an app is sluggish, not just whether a benchmark number is low.

Use the result as a clue, not a diagnosis. A browser test measures performance through the storage access available to the browser. It does not inspect every part of the drive or reproduce every app's workload exactly.

What the result means

Small writes are slow, but large-file speed looks normal

Your storage may handle long, continuous transfers better than lots of separate changes. That pattern can matter when apps update settings, save small files, install or unpack software, or work with folders containing many items. It does not mean every app will feel slow: some tasks depend more on the processor, memory, network, or the app itself.

Try to connect the test to a real symptom. If a large file copies quickly but an app takes a long time to start, storage may be one factor. If only one app is slow, check that app before assuming the drive is at fault.

Both small writes and large-file speed are slow

The slowdown may affect more than small updates. The drive could be busy, nearly full, connected through a slow port or adapter, or experiencing a problem. First check for background transfers and available space. If the computer also freezes, reports read errors, or disconnects an external drive, back up important files before further testing.

Results change a lot between runs

Storage work may be competing with a download, update, cloud backup, or another open app. Power mode and device temperature can also affect some computers. Close unrelated work and compare again, but avoid running tests repeatedly for a long time, especially if the device is hot.

The score is low, but you do not notice a slowdown

A score out of 100 is a quick indication from this test, not a guarantee of how fast every task should feel. Your normal workload may not depend much on small writes, and a browser benchmark cannot represent every program's storage pattern. Do not replace a drive based on one score alone.

How to improve everyday performance

  1. Wait for other storage work to finish. Pause large downloads, file copies, backups, and cloud sync while you compare performance. On Windows 11, check Settings › Windows Update for an update in progress. On macOS, check System Settings › General › Software Update.
  2. Check how much space is free. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. If the drive is nearly full, remove files you no longer need or move large personal files elsewhere. Keep a backup before deleting anything important.
  3. Compare while plugged in. A laptop may reduce performance to save power. On Windows 11, open Settings › System › Power & battery › Power mode and compare with the computer plugged in. On a Mac laptop, check System Settings › Battery › Low Power Mode. Change power settings only for the comparison, then restore your usual choice.
  4. Check which drive is involved. If the slow work happens on an external drive, connect it directly to another compatible port and try a known-good cable. A hub, adapter, or damaged cable can limit transfers or cause interruptions.
  5. Restart and check again. A restart can clear a stuck process that is constantly reading or writing files. Afterward, test once before opening your usual apps, then see whether the everyday slowdown remains.
  6. Update the system and storage software. Install available operating system updates and use the computer or drive maker's official instructions for storage firmware or drivers. Avoid random driver downloads, and do not update firmware while the computer may lose power.

When the drive may need attention

A slow small-write result by itself does not prove that a drive is failing. Stronger warning signs include repeated read or write errors, files that become unreadable, frequent freezes during file access, or an external drive that disconnects. If you see these signs, copy important files to another device before trying repairs or more tests.

If the same slowdown continues across several apps after background work and connection issues are ruled out, check the drive's health with the computer maker's supported diagnostics or ask a repair shop to inspect it. A drive that reports errors or cannot reliably save files may need replacement, even if some large transfers still appear fast.

Why small writes differ from copying a large file

A large copy can often be written in a mostly continuous stream. Small-write tasks may involve many separate locations, file updates, and bits of information that describe where files are stored. The drive and operating system have more work to coordinate, so performance on one kind of task does not predict the other perfectly.

That is why a fast movie copy does not rule out a storage bottleneck in an app that constantly updates small files. It is also why a low small-write result does not prove that storage causes every delay. Use the test to decide what to check next, then judge the change by the tasks that matter to you.