convex-performance-audit

Slow Convex reads and excessive mutation retries often stem from read amplification or OCC conflicts. Diagnose these performance bottlenecks by tracing full read/write sets and mapping symptoms to specific remediation rules for hot paths.

Audit Convex subscription overhead and query limits by running `npx convex insights --details` to gather deployment health signals. Route the identified symptoms to matching guidance for subscription cost or function execution budget issues.

Fix high bytes and doc reads in Convex by applying signal-driven performance triage to identify read amplification. Trace one concrete user flow end-to-end and propose the smallest high-impact fix within the relevant reference rules.

You can trace specific user flows to fix Convex function budget errors by auditing sibling functions touching the same tables. Verify no regressions occur after changes by checking result parity and confirming execution limits are resolved.

Diagnose Convex OCC conflicts without deployment insights by performing a targeted code audit. Look for code symptoms like high mutation retries or high subscription counts and map them to specific reference rules for remediation.