domains / families / software-engineering / audit-performance

audit-performance

separate

Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes.

When to use

• find performance issues
• investigate freezes/500s/OOMs
• review retries or polling for no-progress loops
• rank a performance backlog
• implement the next simple performance fixes

When not to use

• optimize information away when it may soon support product UI or behavior
• build a projection, cache, cursor state machine, or alternate read model just to reduce a modest fixed query count
• prioritize by scary-looking counts alone

Skill page

Source