Storage rest API

Question

how to resolve storage rest api latency.please share best practices and share the details of sdks and thier latencies if any.

Answer 1

Hi @raja dev ,

Azure Storage REST API latency is usually influenced by client‑side network factors and request patterns rather than the REST API itself. Here are some best practices to reduce latency:

1. Deploy client and storage in the same region to minimize network RTT. Cross‑region access significantly increases latency.
2. Avoid oversized range reads when reading blobs; large ranges can increase response time.
3. Check DNS resolution behavior—stale or misconfigured DNS can easily add 80–100 ms per request.
4. Use parallel/asynchronous requests instead of sequential calls to improve throughput and perceived latency.
5. Prefer Azure Storage SDKs where possible. SDKs use the same REST APIs but add client‑side optimizations such as connection pooling, retries, and efficient async patterns, which typically provide more stable performance in production.

Azure does not publish fixed latency numbers for REST or SDKs, as latency depends on region, network path, request type, and workload characteristics.

If the issue persists, please share the below over Private message:

• Which SDK or REST client you’re using
• Operation type (read/write/list)
• Whether the client and storage account are in the same region

References:

• Azure Storage REST API Reference
• Troubleshoot performance in Azure storage accounts

Note: This is drafted with the help of AI.

Kindly let us know if the above helps or you need further assistance on this issue.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Answer 2

For REST latency, pin the client to the storage region and avoid oversized range reads. If it still spikes, check for stale DNS. a bad resolve can easily add 80–100 ms. Seen this one bite more than once.