convex-performance-audit

A Convex performance audit diagnoses hot path reads, subscription costs, and OCC conflicts by tracing reads and writes across a specific user flow. It evaluates function budgets and applies built-in reference fixes to reduce reactive invalidation.

Reduce Convex subscription costs by tracing reactive invalidation across user flows and applying guided best practices. The audit identifies excessive subscriptions and implements fixes following a reference-guided order to minimize reactive updates.

Convex apps experience OCC conflicts and write contention when concurrent operations compete for the same documents. The performance audit identifies these conflicts by tracing write paths across user flows and applies best practice fixes to reduce contention.

Yes, the Convex performance audit evaluates function budgets by enforcing one concrete user flow as the audit scope. It traces all reads and writes across that path to ensure operations stay within optimal resource limits.

You should escalate to migration-safe patterns during a Convex performance audit when standard reference-guided fixes cannot resolve hot path reads or write contention. This coordinates with migration helper workflows to safely restructure problematic data patterns.