convex-performance-audit

OCC conflicts in Convex are caused by concurrent writes invalidating reactive subscriptions, leading to write amplification and performance degradation. An audit examines these signals and applies patterns from occ-conflicts.md to resolve the contention safely.

The best way to reduce subscription cost and reactive invalidations in Convex is to analyze subscription code paths against function budgets and apply aggregation patterns. Auditing identifies frequent invalidations and proposes minimal adjustments for verifiable performance gains.

To audit Convex functions against read and mutation budgets, you analyze hot-path symptoms like excessive mutations and high bytes read. The audit cross-references function logic with function-budget.md to ensure operations stay within safe performance limits.

Yes, this Convex performance audit works across pages with slow UI, high bytes read, or OCC conflicts. It requires examining code paths and signals to identify the problem class and apply targeted fixes from matching reference files like subscription-cost.md.

Write amplification and frequent invalidations in a Convex app occur when reactive subscription queries are overly broad, causing cascading database reads on mutations. An audit detects these hot-path symptoms and recommends structural fixes to minimize reactive invalidations.