convex-performance-audit

Diagnose and optimize performance bottlenecks in Convex applications by auditing read amplification, write contention, and subscription costs.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/elcokiin/peluqueria --skill convex-performance-audit-elcokiin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/elcokiin/peluqueria/tree/main/packages/backend/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/elcokiin/peluqueria --skill convex-performance-audit-elcokiin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses performance bottlenecks, high latency, and excessive costs in Convex applications by identifying inefficient read/write patterns and subscription overhead.

Core Features & Use Cases

  • Performance Diagnosis: Analyzes hot-path reads, write contention, and function budget usage.
  • Optimization Strategies: Provides actionable guidance on implementing digest tables, batching mutations, and managing reactive subscription costs.
  • Use Case: Use this skill when your application experiences OCC conflict errors, high document read counts in Convex insights, or sluggish UI updates due to excessive reactive re-renders.

Quick Start

Run the convex-performance-audit skill to analyze the current deployment and identify high-latency read paths.

Frequently Asked Questions about convex-performance-audit

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

FAQPage Schema
Why does my Convex app have high latency and excessive document read counts?

OCC conflicts in Convex arise from write contention when multiple transactions target the same documents. Auditing write contention patterns and batching mutations helps manage transactional integrity and reduce these conflict errors.

How do I optimize reactive subscription costs in Convex?

Optimizing subscription costs involves managing reactive query re-renders and implementing digest tables. This reduces unnecessary data fetching and controls sluggish UI updates caused by excessive reactive query management overhead.

What is the best way to reduce read amplification in a production-scale Convex application?

Reducing read amplification requires diagnosing hot-path reads and applying optimization strategies like digest tables. This ensures efficient data access and controls function budget limits within the Convex ecosystem.

Can I use a performance audit to fix Convex function budget limits?

Yes, a performance audit analyzes function budget usage and identifies high-latency read paths. By optimizing data access and batching mutations, you can satisfy transactional integrity requirements and stay within budget limits.

How do I stop Convex UI re-renders from causing sluggish updates?

Sluggish UI updates in Convex are caused by excessive reactive subscription re-renders. Auditing subscription costs and implementing digest tables optimizes reactive query management and resolves the sluggishness.