convex-performance-audit

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

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/jcodog/CoD-Stats-Tracker --skill convex-performance-audit-jcodog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/jcodog/CoD-Stats-Tracker/tree/main/packages/backend/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/jcodog/CoD-Stats-Tracker --skill convex-performance-audit-jcodog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses performance bottlenecks in Convex applications, such as slow page loads, high database costs, and concurrency conflicts, by providing a structured diagnostic and optimization workflow.

Core Features & Use Cases

  • Performance Diagnosis: Analyzes read/write patterns to identify high-cost operations, subscription bloat, and OCC conflicts.
  • Optimization Strategies: Provides actionable guidance on implementing digest tables, batching mutations, and refining reactive query scopes.
  • Use Case: Use this skill when your Convex dashboard reports high document read counts or when users experience latency during high-traffic ranked match logging sessions.

Quick Start

Run the convex-performance-audit skill to analyze the current deployment and identify the primary cause of high latency in the match logging flow.

Frequently Asked Questions about convex-performance-audit

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

FAQPage Schema
How do I optimize Convex application latency and reduce high database read counts?

To optimize Convex application latency, audit hot-path reads to identify high-cost operations and refine reactive query scopes. Analyzing read and write patterns helps reduce document read counts and resolve slow page loads.

What causes optimistic concurrency control conflicts in Convex and how can I resolve them?

Optimistic concurrency control conflicts in Convex occur when concurrent transactions contest write operations. Resolve OCC conflicts by batching mutations and implementing digest tables to manage write contention and ensure transactional integrity.

How do I reduce subscription costs and bloat in a production Convex backend?

Reduce subscription costs in a Convex backend by refining reactive query scopes to limit unnecessary data tracking. Auditing subscription bloat identifies inefficient reactive queries driving up database costs and latency.

What is the best way to handle function limit errors and write contention during high-traffic Convex mutations?

Handle Convex function limit errors by batching mutations to reduce write contention during high-traffic sessions. Diagnosing hot-path writes identifies bottlenecks causing concurrency conflicts in ranked match logging.

Does this performance audit workflow apply to production-grade Convex backends with ranked match logging?

Yes, this performance audit workflow specifically targets production-grade Convex backends experiencing latency and function limit errors. It diagnoses write contention and high document read counts during high-traffic ranked match logging sessions.