Name the capacity or data-movement limit
An SSD can reduce loading and asset-delivery delays when storage is the constrained stage. It does not increase GPU shader speed or remove a CPU simulation ceiling. Prove the storage link by aligning frame-time spikes with I/O and repeating the same traversal after the data is cached.
Capacity, bandwidth, channel layout and data movement are different limits and require different evidence. First hypothesis to test: Open worlds request assets during movement.
Capacity, bandwidth and transfer limits to separate
Compare two early explanations: (1) Open worlds request assets during movement; and (2) Paging creates storage traffic when RAM is full. They can resemble one another in a headline result but predict different responses to the checks below.
Signals to capture during the event
- Open worlds request assets during movement.
- Paging creates storage traffic when RAM is full.
- Antivirus scans compete for I/O.
- Shader compilation can coincide with disk access.
Reproduce the memory-heavy event while logging allocation, committed use, faults or transfers from the same pass.
Shortcuts that produce the wrong diagnosis
Each shortcut below removes context that the diagnosis needs. Treat it as a reason to repeat the capture, not as evidence for a new component.
False leads to clear
- Blaming every stutter on the drive.
- Ignoring RAM-driven paging.
- Comparing different game patches.
Reproduce the memory-heavy event
Use the first two controls in order: Log disk latency, throughput and active time; then Repeat a fast traversal route. This establishes whether the first observation survives a controlled comparison.
One-variable test sequence
- Log disk latency, throughput and active time.
- Repeat a fast traversal route.
- Check RAM pressure and hard faults.
- Compare cold and warm passes.
Change one capacity or configuration variable and verify that the relevant stall, low or completion time responds.
Connect allocation and traffic to the stall
Observation, isolation step and diagnosis
| Observation | Controlled change | Likely interpretation |
|---|---|---|
| Cold pass stalls, warm pass smooth | Repeat after restart | Caching or compilation contributes |
| Spikes align with high disk latency | Move the game to SSD | Storage delivery is supported |
| No I/O during spikes | Inspect CPU and GPU events | Storage is unlikely to be primary |
When the observation is “Cold pass stalls, warm pass smooth,” apply “repeat after restart.” The evidence table reads the response as follows: Caching or compilation contributes.
Fix the memory path that actually ran short
Upgrade storage for demonstrated loading or streaming problems and for overall responsiveness. Keep enough RAM to avoid unnecessary paging. A faster drive is valuable, but it should not be marketed as a universal FPS upgrade.
Diagnostic record
Record capacity, channel mode, rate, timings, committed use, VRAM use and any storage or bus traffic tied to the event.
- disk latency
- active time
- read queue
- asset request
- decompression
- cold traversal
- warm traversal
- paging traffic
Decision boundary: The decision above should also survive the most likely shortcut: blaming every stutter on the drive.
Related memory guides
Build the cluster one verified step at a time
Compare this result with DDR4 vs DDR5: Can Memory Limit a Gaming PC?, Single-Channel vs Dual-Channel RAM Bottlenecks, and 16 GB vs 32 GB RAM for Gaming Bottlenecks; keep the same workload and baseline while testing the competing explanations.
Technical sources
References for the measurement method
