The MSDN article that describes Nagle's algorithm (http://msdn.microsoft.com/en-us/library/windowsazure/hh697709.aspx) should highlight the performance gains from disabling Nagle's algorithm.
In our case, disabling that algorithm yielded an order of magnitude improvement in latency (from 300 to 30 ms). This is a vital piece of information that is not highlighted in performance optimization documentation for Azure.
It may even be worthwhile to consider disabling Nagle's algorithm by default, or provide some default configuration examples that remark on this algorithm.1 vote
We have documented the impact of Nagle’s Algorithm on the Windows Azure Storage Team Blog (http://blogs.msdn.com/b/windowsazurestorage/archive/2010/06/25/nagle-s-algorithm-is-not-friendly-towards-small-requests.aspx), and will work to make it more prevalent in our other performance-related documentation.
Does what it says on the tin....really need better search capabilities over azure table storage.931 votes
A common need for users of Azure Table Storage is searching data in a Table using query patterns other than those that Table Storage provides efficiently, namely key lookups and partition scans. Using Azure Search, you can index and search Table Storage data (using full text search, filters, facets, custom scoring, etc.) and capture incremental changes in the data on a schedule, all without writing any code. To learn more, check out Indexing Azure Table Storage with Azure Search: https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables
- Don't see your idea?