convex-performance-audit

Diagnose slow Convex pages and high OCC conflicts by gathering signals from deployment Health insights and `npx convex insights --details`, then tracing the user flow to map read/write sets. This identifies whether bottlenecks stem from read amplification or write contention.

OCC conflicts and mutation retries in Convex are caused by write contention on hot paths. Auditing traces the user flow to map write sets and applies least-invasive reference-guided fixes to reduce contention and eliminate excessive retries.

Reduce high insight bytes and document reads in Convex subscriptions by auditing the full read set and sibling endpoints. The audit identifies subscription invalidation costs and applies targeted fixes to eliminate unnecessary reactivity and reads.

Convex functions approach execution or transaction limits when read/write sets expand uncontrollably. Auditing traces the full flow to identify budget risks and applies guardrail-compliant, least-invasive fixes to reduce cost and prevent failures.

You can audit Convex performance without Health insights by falling back to a code-first audit. The workflow traces a single concrete user flow to map the full read/write set, including sibling endpoints and reactivity touchpoints, to identify bottlenecks.

Verify Convex performance fixes by confirming correctness, expected read/write elimination, fallback behavior, and consistent sibling updates. This verification step ensures the applied least-invasive changes reduce cost without introducing new issues.