First 10 Minutes: Performance¶

Use this checklist when the symptom is slow upload/download, latency growth, reduced throughput, or 429/503 throttling.

mermaid flowchart TD A[Performance complaint] --> B{429 or 503?} B -->|Yes| C[Check account pressure and throttling] B -->|No| D{Server latency high?} D -->|Yes| E[Check transaction spikes and partitioning] D -->|No| F[Check client path concurrency and RTT]

Checklist¶

1. Capture the operation type, object size profile, concurrency settings, and region pair.
2. Check Azure Monitor metrics for Transactions, SuccessE2ELatency, SuccessServerLatency, Availability, Ingress, and Egress.
3. Separate server-side latency from client-side end-to-end latency.
4. Identify whether 429 or 503 exists; if yes, assume throttling is possible until disproven.
5. Check whether the workload is dominated by many small files, single-thread transfers, or long-distance clients.
6. Re-test with representative transfer tooling such as AzCopy and controlled concurrency.

Route to playbooks¶

• Slow throughput without clear throttling → Slow Upload / Download
• 429, 503, or burst-driven account pressure → Throttling and Performance Issues
• Recovery outcome depends on prior protection settings → Data Protection and Recovery Issues

See Also¶

• Playbooks: Performance
• Evidence Map
• Performance Best Practices

Sources¶

• Azure Blob Storage performance checklist
• Optimize AzCopy performance
• Scalability and performance targets for standard storage accounts