convex-performance-audit

Diagnose Convex performance bottlenecks in hot-path reads, write contention, and subscription invalidation.

Updated Dec 23, 2021
One-click install
npx skills add https://github.com/dvakatsiienko/bytes --skill convex-performance-audit-dvakatsiienko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/dvakatsiienko/bytes/tree/main/apps/x-com-chat/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/dvakatsiienko/bytes --skill convex-performance-audit-dvakatsiienko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses and mitigates Convex performance bottlenecks across hot-path reads, write contention, and reactive invalidation, enabling faster, more predictable apps.

Core Features & Use Cases

  • Problem mapping: maps symptoms from insights, dashboards, and code audits to concrete problem classes such as hot-path reads, OCC conflicts, and subscription cost.
  • Guided fixes: prescribes minimal, migration-safe changes aligned with Convex best practices, including index adjustments, denormalization, and read-path optimizations.
  • Workflow support: provides a repeatable audit workflow with references and escalation steps for larger refactors.

Quick Start

Run an audit, identify the strongest signal, then apply the smallest high-impact fix first.

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 high subscription costs and OCC conflicts in my Convex app?

Diagnose Convex subscription costs and OCC conflicts by mapping dashboard insights and symptoms to problem classes, then prescribing migration-safe read-path optimizations and index adjustments.

What is the best way to optimize Convex hot-path reads causing performance bottlenecks?

Optimize Convex hot-path reads by auditing insights outputs for high byte counts, then applying minimal fixes like denormalization and index adjustments aligned with Convex best practices.

Why does my Convex app have heavy mutation retry rates and elevated subscription costs?

Heavy mutation retry rates and elevated subscription costs in Convex stem from write contention and reactive invalidation, requiring an audit to map symptoms and apply targeted refactors.

How do I fix Convex write contention without breaking existing migrations?

Fix Convex write contention by applying minimal, migration-safe changes such as index adjustments and denormalization, guided by a repeatable audit workflow that maps symptoms to problem classes.

When should I run a full Convex performance audit on my application?

Run a Convex performance audit when insights flag high bytes, OCC conflicts, heavy mutation retry rates, or elevated subscription costs across multiple pages and functions in your app.

Can I use a structured workflow to reduce Convex subscription invalidation overhead?

Reduce Convex subscription invalidation overhead using a repeatable audit workflow that reviews insights, identifies the strongest signal, and prescribes the smallest high-impact fix first.