Hello - I was doing some experiment with azure table store and I found this.

I created a table (west us region) with just one record in it.

Scenario1:

I tried accessing the record from console application running on my devbox and it took consistently  400 milliseconds to access the record based on partition and row key.

Sceanrio2:

I created a cloud service (wcf - running on my devbox with azure emulator) and ran the same query and it took consistently 5 milliseconds (to fetch that record from the same west us region).

Question:

Why I see this difference? 400 ms vs 5 ms ? Console Vs cloud service?

-PPT

Hello,
We are researching on the query and would get back to you soon on this. we appreciate your time and patience in this matter.

Best Regards,
Kamalakar

Hi PPT,<o:p></o:p>

If your console app is running outside of the Microsoft data center network such as work or home, it is possible that this is due to potential network issues. You can monitor Azure Storage metrics and compare AverageE2Elatency and AverageServerLatency, to identify what caused it.<o:p></o:p>

The following article has all the information that you need to troubleshoot this issue: https://azure.microsoft.com/en-us/documentation/articles/storage-monitoring-diagnosing-troubleshooting/#metrics-show-high-AverageE2ELatency-and-low-AverageServerLatency<o:p></o:p>

Please especially look at the following section:<o:p></o:p>

Metrics show high AverageE2ELatency and low AverageServerLatency<o:p></o:p>

Metrics show low AverageE2ELatency and low AverageServerLatency but the client is experiencing high latency<o:p></o:p>

Metrics show high AverageServerLatency

<o:p></o:p>

• Proposed as answer by Aung Oo - Microsoft 2 hours 48 minutes ago