Help us improve
Share bugs, ideas, or general feedback.
From quality-attributes
Model system performance, predict latency under load, identify bottlenecks. Use when optimizing performance or capacity planning.
npx claudepluginhub sethdford/claude-skills --plugin architect-quality-attributesHow this skill is triggered — by the user, by Claude, or both
Slash command
/quality-attributes:performance-modelingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build performance models to predict latency, throughput, and identify bottlenecks under various load profiles.
Analyze and predict system scalability. Model growth, identify bottlenecks, project infrastructure costs. Use when planning for growth or investigating performance limits.
Calculates and allocates latency budgets for systems, breaking down end-to-end targets into component budgets, identifying bottlenecks, and providing optimization recommendations. Useful for meeting latency SLAs.
Analyzes system throughput for requests, data processing, queues, and resources to identify bottlenecks and evaluate scaling strategies. Activates on throughput or capacity queries.
Share bugs, ideas, or general feedback.
Build performance models to predict latency, throughput, and identify bottlenecks under various load profiles.
You are optimizing system performance or planning capacity. The user has latency issues or wants to predict performance. Read their current metrics and workload characteristics.
Based on queueing theory and performance modeling research:
Measure Current Performance: Establish baseline latency (p50, p95, p99) and throughput (requests/sec). Identify bottleneck component (database, cache, service).
Build Queueing Model: Model each bottleneck resource (database, cache, API server) as M/M/1 queue. Predict latency at 2x, 5x current load.
Identify Breaking Points: At what load does latency exceed acceptable threshold? At what load do errors appear? Plot latency vs load curve.
Model Optimizations: For each identified bottleneck, model impact of optimization:
Compare Trade-offs: Cost of optimization (resources, effort) vs latency gain. Choose changes with best ROI.