Identify the graphics-side constraint
Resolution scale, ray tracing, shadows, volumetrics, reflections and post-processing often affect GPU time more than textures do when VRAM is sufficient. Preset names hide implementation differences, so change one setting group and measure the exact scene instead of copying a universal ranking.
GPU execution time, VRAM pressure and a deliberate frame cap can all produce different meanings behind one utilization number. First hypothesis to test: Pixel-linked effects scale with internal resolution.
Rendering, memory and clock limits to separate
Compare two early explanations: (1) Pixel-linked effects scale with internal resolution; and (2) Ray effects add traversal and denoising. They can resemble one another in a headline result but predict different responses to the checks below.
Signals to capture during the event
- Pixel-linked effects scale with internal resolution.
- Ray effects add traversal and denoising.
- Volumetrics and shadows use repeated samples.
- Textures mainly become costly when capacity is exceeded.
Keep the camera path fixed and change one rendering cost, such as internal resolution, textures or ray tracing.
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
- Changing the full preset at once.
- Assuming texture quality always costs FPS.
- Ignoring the CPU ceiling at low settings.
Change one graphics cost at a time
Use the first two controls in order: Record the original image and frame time; then Change one setting group by one step. This establishes whether the first observation survives a controlled comparison.
One-variable test sequence
- Record the original image and frame time.
- Change one setting group by one step.
- Repeat a demanding but stable camera path.
- Restore the setting before testing the next group.
Demand the predicted GPU-time or memory response before treating a graphics setting or new card as the solution.
Read GPU time, memory and clocks together
Observation, isolation step and diagnosis
| Observation | Controlled change | Likely interpretation |
|---|---|---|
| Large gain, small visual loss | Keep the change | High-value tuning is available |
| No gain from lower textures | Restore quality | VRAM was not the limit |
| FPS stops scaling at low settings | Inspect CPU time | The bottleneck has moved |
When the observation is “Large gain, small visual loss,” apply “keep the change.” The evidence table reads the response as follows: High-value tuning is available.
Choose a setting fix or graphics upgrade
Tune to a frame-time budget, not the lowest preset. Preserve settings whose visual value is high and reduce the expensive effects that matter least to you. A GPU upgrade becomes rational when acceptable image quality still misses the target after stable clocks and sensible tuning.
Diagnostic record
Record base-frame GPU time, clocks, power, temperature, dedicated memory and the exact graphics preset.
- resolution scale
- volumetric samples
- shadow cascade
- reflection quality
- ambient occlusion
- texture pool
- preset delta
- visual comparison
Decision boundary: The decision above should also survive the most likely shortcut: changing the full preset at once.
Related gpu guides
Build the cluster one verified step at a time
Compare this result with Shader Compilation Stutter vs a Hardware Bottleneck, Ray Tracing Bottlenecks: CPU, GPU and VRAM, and VRAM Bottleneck Signs and Tests; keep the same workload and baseline while testing the competing explanations.
Technical sources
References for the measurement method
