You copy a huge folder to your new SSD, watch it fly at 3,000 MB/s, then see it collapse to 400 MB/s halfway through. Nothing is broken. You have simply exhausted the drive’s fast SLC write cache and fallen back to its native speed. Understanding this behavior, and a few ways to soften it, saves a lot of needless panic.
What Is the SLC Cache?
Most consumer SSDs store data at three or four bits per cell (TLC or QLC), which is dense but slow to write. To feel fast, the drive treats a slice of that flash as pseudo-SLC (one bit per cell), which is very fast. Incoming writes land in this cache first, then migrate to dense storage in the background. When the cache fills during a big transfer, writes hit the slow native flash directly.
Why Bigger and Fuller Drives Behave Differently
The cache is often dynamic, borrowing from free space. A near-empty 2TB drive might sustain fast writes for 200GB+; the same drive at 90% full might have only 15GB of cache and slow almost immediately. QLC drives fall further and harder than TLC ones.
| Drive Type | Cached Speed | Post-Cache Native Speed |
|---|---|---|
| Gen4 TLC (quality) | ~5,000-7,000 MB/s | ~1,000-1,800 MB/s |
| Gen4 QLC (budget) | ~4,000-5,000 MB/s | ~80-400 MB/s |
| DRAM-less budget SSD | ~2,000-3,500 MB/s | ~300-900 MB/s |
| SATA TLC SSD | ~550 MB/s | ~350-500 MB/s |
How to Reduce the Slowdown
1. Keep 15-20% Free Space
Dynamic SLC cache shrinks as the drive fills. Leaving a fifth of the drive empty preserves a large cache and better sustained speed. This is the single most effective fix.
2. Buy TLC, Not QLC, for Heavy Writes
If you routinely move giant files, choose a TLC drive with DRAM. QLC is fine for a mostly-read game library but punishing for sustained writes.
3. Break Up Massive Transfers
Copying in smaller batches with pauses lets the cache flush to native flash between rounds, so each batch starts fast again.
When Slow Writes Signal a Real Problem
Cache exhaustion is normal and temporary. But if even small writes are slow, or the drive is slow at idle after cooling down, suspect a full drive, thermal throttling, a failing drive (check SMART), or a bad SATA cable. Rule those out before blaming the cache.
Frequently Asked Questions
Is post-cache slowdown a sign my SSD is defective?
No. It is expected behavior for every consumer SSD. The drive is working as designed; you have just written more at once than the fast cache can hold. Reviews measuring “sustained write” reveal this ceiling.
Does gaming ever hit the cache limit?
Almost never. Games read far more than they write, and installs pause and resume in chunks. Cache exhaustion mainly bites during video editing, backups, and disk-to-disk copies of hundreds of gigabytes.
How to Measure Your Drive’s True Sustained Speed
Synthetic benchmarks like CrystalDiskMark test small data sizes that fit entirely inside the SLC cache, so they report the fast cached figure, not real-world sustained speed. To see the true post-cache number, copy a genuinely large file, 100GB or more, from one fast drive to the SSD and watch the transfer rate in the last third of the copy. That steady-state figure is what you will actually get when installing a huge game or exporting a long video. It is often a fraction of the box’s headline number, especially on QLC drives.
Why This Rarely Matters for Gamers
It is worth repeating: cache exhaustion is a write-side concern, and gaming is overwhelmingly a read workload. Load times depend on random read performance, which stays consistent regardless of the write cache. So unless you record and export gameplay footage or move enormous files regularly, the sustained-write ceiling is a spec you can safely ignore in favor of capacity and price.
Bottom Line
Slow writes after a fast start are the SLC cache filling, not a fault. Keep the drive 15-20% empty, prefer TLC-with-DRAM for write-heavy work, and split enormous transfers. For gaming, it is a non-issue; for creators, drive choice and free space are what keep speeds high.
