I am launching an Azure web role that stores very small drops in Azure storage. (Blob downloads are from the server, not from the browser.) I was looking for stack overflow and the rest of the Internet for tips on optimizing storage performance, and I believe that I checked and implemented all the usual suspects: loading asynchronous mode, allowing unlimited outgoing Web connections (which now appear to be the default settings for web roles and no longer need to be explicitly specified in the web.config file or in the code).
Changing the number of simultaneous downloads that I allow has a certain difference, but no matter what I tried, it seems to me max at about 1000 download blocks per second . This happens when you run the Azure web role in the same region as the vault account (East US). My bet on starting this house due to a good internet connection is not much less than ~ 700 blobs / sec, which apparently tells me that this is not network latency that limits speed, this is the actual processing time of the storage service.
I would not consider these tariffs as terrible for this type of service, but I read that Microsoft has a speed of ~ 20,000 storage transactions per second , so I was little disappointed with these results.
I would like to receive feedback from those who really tried to push the limits of the blob repository. Seems like around 1000 small downloads per second? Or maybe something else I should do to improve this? I will send the code if necessary, but I would prefer not to receive speculative answers, I would like to hear from developers who can either confirm that my results are reasonable, or that they have seen much higher bandwidth.
I must add that I am currently running this in a small web role. I tried this also as an average website and did not see any significant differences.
EDIT:
. , , , 200 . -, Azure, : " ". , , , . .