Performance and Scalability Diagnosis
Use Google SRE monitoring guidance for operational signals. The diagnosis and capacity workflow below is this catalog's review contract; neither the reference nor a signal alone proves a cause or scaling limit.
Workflow
- Define the affected journey, workload, percentile, units, environment, time window, and expected objective.
- Capture a reproducible baseline and separate client, network, queue, service, datastore, and dependency time.
- Form competing hypotheses for latency, saturation, allocation, locking, retries, fan-out, and load amplification.
- Use profiles, traces, query plans, metrics, and controlled load evidence to discriminate among hypotheses.
- Identify the first constrained resource and whether the limit is per request, per instance, or shared.
- Estimate headroom and scaling behavior with explicit assumptions; distinguish measurement from extrapolation.
- Recommend the smallest experiment or remediation capable of falsifying the diagnosis.
Boundaries
- Do not optimize from averages alone when tail behavior matters.
- Do not run load tests against shared or production systems without explicit authorization and safeguards.
- Do not claim scalability from a single local benchmark or an unrepresentative fixture.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Symptom, Baseline, Hypotheses, Measurements, Causal diagnosis, Capacity estimate, and Next experiment.
Example
Synthetic example; not an observed client result.
Input: Latency doubled, but no comparable load or tracing data is available.
Output: The regression is reported, not localized. Establish comparable workload and stage timings before choosing an optimization.
1---2name: diagnose-performance3description: "Diagnoses a slow or overloaded system when asked why latency, throughput, or resource use changed; compares measurements and hypotheses without silently optimizing code."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/diagnose-performance7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Performance and Scalability Diagnosis1617Use [Google SRE monitoring guidance](https://sre.google/sre-book/monitoring-distributed-systems/) for operational signals. The diagnosis and capacity workflow below is this catalog's review contract; neither the reference nor a signal alone proves a cause or scaling limit.1819## Workflow20211. Define the affected journey, workload, percentile, units, environment, time window, and expected objective.222. Capture a reproducible baseline and separate client, network, queue, service, datastore, and dependency time.233. Form competing hypotheses for latency, saturation, allocation, locking, retries, fan-out, and load amplification.244. Use profiles, traces, query plans, metrics, and controlled load evidence to discriminate among hypotheses.255. Identify the first constrained resource and whether the limit is per request, per instance, or shared.266. Estimate headroom and scaling behavior with explicit assumptions; distinguish measurement from extrapolation.277. Recommend the smallest experiment or remediation capable of falsifying the diagnosis.2829## Boundaries3031- Do not optimize from averages alone when tail behavior matters.32- Do not run load tests against shared or production systems without explicit authorization and safeguards.33- Do not claim scalability from a single local benchmark or an unrepresentative fixture.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Symptom, Baseline, Hypotheses, Measurements, Causal diagnosis, Capacity estimate, and Next experiment.4041## Example4243Synthetic example; not an observed client result.4445Input: Latency doubled, but no comparable load or tracing data is available.4647Output: The regression is reported, not localized. Establish comparable workload and stage timings before choosing an optimization.