convex-performance-audit

Audit Convex hot-path reads, write contention, subscription costs, and function budgets.

2|Updated Jul 1, 2025
One-click install
npx skills add https://github.com/RinKhimera/NOMAQbanq --skill convex-performance-audit-rinkhimera
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/RinKhimera/NOMAQbanq/tree/main/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/RinKhimera/NOMAQbanq --skill convex-performance-audit-rinkhimera

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits and optimizes Convex application performance across hot-path reads, write contention, subscription cost, and function limits to reduce latency and waste.

Core Features & Use Cases

  • Diagnose performance bottlenecks in Convex apps, focusing on reads, writes, and reactive patterns.
  • Provide actionable fixes for hot-path constraints, including OCC conflicts, high mutation retries, and bloated payloads.
  • Apply a migration-safe workflow that scopes a single path, traces reads/writes, and fixes sibling patterns consistently.

Quick Start

Analyze a Convex project with suspected performance issues by identifying the strongest signal and proposing the smallest high-impact improvement in the first pass.

Frequently Asked Questions about convex-performance-audit

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

FAQPage Schema
How do I fix high bytes read and slow queries in my Convex app?

Fix slow Convex queries by auditing hot-path reads and tracing scoped paths to identify bloated payloads, then applying stepwise fixes following hot-path guidance to reduce bytes read.

What causes OCC conflicts and high mutation retries in Convex?

OCC conflicts in Convex are caused by write contention on overlapping documents. Resolve them by auditing write contention patterns and mapping the problem class to scoped path tracing references.

How do I reduce subscription costs from costly reactivity patterns in Convex?

Reduce Convex subscription costs by auditing reactive patterns and function budgets. Identify the strongest signal and propose the smallest high-impact improvement in the first pass.

What is the best way to audit Convex function limits and performance bottlenecks?

The best way to audit Convex performance bottlenecks is gathering signals, mapping problem classes to references, and scoping a single path to trace reads and writes for stepwise fixes.

Can I use a stepwise migration-safe workflow to fix Convex performance issues?

Yes, you can fix Convex performance issues using a migration-safe workflow that scopes a single path, traces reads and writes, and fixes sibling patterns consistently across the project.

Why does my Convex app have high latency and waste despite normal function budgets?

High latency and waste in Convex apps often stem from undiagnosed hot-path constraints, including write contention and bloated payloads, which require a full performance audit to resolve.