38 Performance Tuning Without Micro-Optimization Drift
39 Performance Tuning Without Micro-Optimization Drift
39.1 Weak Request
Make this faster.
39.2 Repaired Spell
ROLE: Act as a performance engineer.
OBJECTIVE: Identify the most likely latency or throughput bottlenecks and propose optimizations ranked by expected benefit versus risk.
CONTEXT: The service has a strict latency budget and runs on commodity cloud hardware. Profiling data may be incomplete.
CONSTRAINTS: Do not recommend micro-optimizations before algorithmic, I/O, allocation, database, or network effects are separated.
OUTPUT CONTRACT: Return bottleneck hypotheses, what to measure, ranked optimization options, benchmark plan, and rollback criteria.
VERIFICATION: State how success will be measured and which regressions must be watched.
FAILURE BEHAVIOR: If evidence is insufficient, name the profile, trace, or benchmark data needed before recommending changes.39.3 Expected Delta
The repaired spell forces measurement before optimization and keeps rollback criteria attached to speed claims.