Azure Subscriber Bandwidth

Question

According to this article: https://azure.microsoft.com/en ... Service Bus can process up to 2000 messages per second for each queue / topic. This article: https://azure.microsoft.com/en ... says: "This means that the overall throughput of a partitioned queue or topic is no longer limited to the performance of a single message broker or message store." If we create a partitioned queue / topic, I believe that it creates 16 sections inside. My question is: Does the bandwidth of a split queue / topic increase linearly to 16 x 2000 = 32,000 (approximate)? Or a bandwidth of 2000 msg / sec remains. Can you tell me some throughput metric for split queue / topic? We are currently analyzing a scenario that requires very high bandwidth. Guidance on this will be really helpful.

This question was also posted on the Azure website: https://azure.microsoft.com/en-us/documentation/articles/service-bus-performance-improvements/

Answer 1

Performance depends on several factors. For example, many additional features (such as duplicate detection, sessions, transactions, etc.) will add overhead, which reduces throughput. In case you want to compare this yourself, try running this performance sample: https://github.com/Azure-Samples/service-bus-dotnet-messaging-performance

In addition, since basic / standard are common tenant models, the performance you get today may be different from the performance you get tomorrow. In addition, you may not see the linear scale, as some nodes may be busier than others.

For true predictability, premium is your best bet.