HetCreep Scale Canary (Performance & Resource Allocation Audit)
Audit code for scalability issues, performance bottlenecks, and resource leaks.
Auditing Categories
- O(N^2) Complexity — nested loops over growable collections without indexing or caching (crashes at scale).
- N+1 Database Queries — querying records in a loop instead of a batch JOIN or bulk prefetch.
- Memory Bloat / Leaks — appending to global arrays/maps without clearing them → unbounded growth.
- Blocking Main Loop — synchronous FS ops or CPU-heavy work on the main event thread (lag/hangs).
- Resource Leakage — streams, connections, or handles left open without a
finallyclose.
Per-ORM N+1 shapes, per-stack blocking patterns, and what NOT to flag: read references/checks.md before scanning.
Fix mode (choice-gated)
In Agent Context, after the report, present via ask_question:
- Apply safe optimizations: async-ify synchronous file ops; insert
finallyblocks for stream closing. Each fix: checkpoint (git stash/commit in a git repo; else copy the file aside — never assume git) → apply → build + tests → auto-revert if newly red. - Let me pick: user selects specific optimizations.
- Report only: exit unchanged.
Grants & denials (CLASSIFY-BLOCK)
| class | step it powers | grant | on denial |
|---|---|---|---|
| read | scan loops/queries/caches for the categories above | Read·Grep·Glob |
refuse that file, name it — never a clean bill |
| write | Fix mode's safe-optimization apply, incl. checkpoint → build+tests → auto-revert if newly red | Edit·Bash (checkpoint/build/revert need exec) |
report the fix as NOT applied AND the checkpoint/revert as NOT available, never claim done |
Output
| file:line | bottleneck | severity | finding | optimization plan |
Severity: CRITICAL (O(N^2) on user-facing API / unclosed file handles) · HIGH (N+1 query pattern / blocking main loop) · MEDIUM (unbounded cache growth) · LOW (minor efficiency suggestions)