Compare the same requirement
Read every row against the application you intend to operate, then test the assumption named in the example.
Scroll horizontally to read every column on a small screen.
| Criterion | Larger allocation | Reduce or reschedule task |
|---|---|---|
| Signal | Sustained known workload | One import, cache or runaway worker |
| Change | Adds monthly resources | Changes code, limits or schedule |
| Risk | Cost without fixing leak | May slow intended work |
| Verification | Same workload with headroom | Same result with lower peak |
| Rollback | Return to prior plan later | Restore prior task behavior |
Example choice
If a nightly import alone exhausts memory, cap concurrency or move it outside peak traffic and measure again. If ordinary app plus database demand remains above the written budget, a larger plan is defensible.
Decision
Record the process and time window that caused pressure before spending or tuning.