Geek Answers Handbook

Storage performance in Azure - REST vs. Storageclient

I am working with Azure Desktop Storage and trying to find the best way to improve performance. The queries that I execute are very simple - either the exact selection using the section key, and the line key, or the where clause with a list (for example, WHERE x == 1 or x == 2 or x == 3, etc.) . As soon as I return the data, I do not track them in the context of the data (there is no need to track changes, etc.). Saving data is similar, so I add it to the context to enable saving.

I am currently using the .NET library (repository client). Since I do not use change tracking and other TableServiceContext functions, I am thinking about using the HTTP API directly. Has anyone tried both options? If so, what difference in performance have you seen?

Thanks Erick

+7
source share
2 answers

Table storage can be a slightly volatile beast to optimize performance. There are many factors that will affect it. Here are just a few of them from head to head:

  • The use of a section key in each request is required. If you do not do this, you are doing it wrong. If you use a single PC and one RK (and only those two), it is no longer a request, but a GET resource and should be relatively instantaneous.
  • Do not use OR-based queries. This will result in a full table scan, and your performance will be terrible. Instead, parallelize these queries in the OR statement.
  • A separation strategy will go a long way. How many partitions you have and how often you hit them (to warm them up and make the underlying partition servers load the balance) will cause serious differences. Partition size is also very important here. Sequential partition keys are often bad ideas.
  • Small queries can come in handy when disabling nuggling (as mentioned earlier).
  • Disabling context tracking and continuing 100 ( see here ) can also help.

There are many more, I suppose, it depends on your application. However, the ones I mention are usually the ones I start with.

+10
source

Did you turn off the Nagl?

Interest:

+2
source

More articles:


All Articles