A performance diet comes back as "it feels unstable"
Deploy and infrastructure
Symptom
Tightened cache and preload to protect frame rate. Frames held, but tiles filled late and the screen sat empty, and that felt more unstable than the stutter did.
Cause
Load speed and frame rate are different axes, but a diet treats them as one knob and tightens both.
Fix
- Measure the two axes separately. Watch fps and time-to-tiles-filled together.
- Record the values before tightening so you can revert. The revert was only possible because the old values were in a previous log.
- A loading indicator that makes the wait visible is also a perceived-performance tool (without touching the values).