convex-performance-audit

Analyze Convex app reads, subscriptions, and reactive invalidations to identify performance bottlenecks.

Updated Aug 23, 2026

Search Tags:#performance #audit #convex #hot-path #occ-conflicts #subscription-cost

Ready to run

npx skills add https://github.com/awfixers-stuff/corp.awfixer.me --skill convex-performance-audit-awfixers-stuff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/awfixers-stuff/corp.awfixer.me/tree/main/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/awfixers-stuff/corp.awfixer.me --skill convex-performance-audit-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits Convex apps to identify performance bottlenecks across reads, subscriptions, OCC conflicts, and write amplification, enabling targeted, measured fixes.

Core Features & Use Cases

Detect hot-path symptoms such as high bytes read, excessive mutations, and frequent invalidations.
Recommend minimal, safe fixes aligned with Convex best practices (hot-path rules, function budgets, and aggregation patterns).
Real-world use: pinpoint a slow page and propose a small, high-impact adjustment with verifiable gains.

Quick Start

Run a structured Convex performance audit on the target app using the strongest signal to identify a problem class and propose a minimal, high-impact fix.

Frequently Asked Questions about convex-performance-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose slow UI and high bytes read in my Convex app?▼

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.

What is the best way to reduce subscription cost and reactive invalidations in Convex?▼

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.

How do I audit Convex functions to stay within read and mutation budgets?▼

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.

Does this Convex performance audit work for both pages with slow UI and high OCC conflicts?▼

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.

Why does my Convex app experience write amplification and frequent invalidations?▼

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.