Would Partitioning in Service Bus queue increase TPS?

Deepanshu Goyal 1

Dear Azure Team, I need to know for sure that If I use partitioning in Azure service bus, would it increase the TPS from 2000 per second.

https://github.com/Huachao/azure-content/blob/master/articles/service-bus/service-bus-azure-and-service-bus-queues-compared-contrasted.md#:~:text=treated%20as%20billable)-,Additional%20information,%2C%20Get%2C%20or%20Delete%20operation.

on above link it is mentioned that TPS is 2000 for a queue. So we need to increase this TPS. Hence would partitioning help us in achieving higher TPS?

Thanks.

1 answer

Mike Urnun 9,811 Reputation points Microsoft Employee

2022-02-23T02:31:37.207+00:00

Hello @Deepanshu Goyal - Welcome to MS Q&A!

Yes, Partitioning will absolutely improve the throughput of your Queues & Topics (and is the right feature to configure for processing a high volume of messages) provided that your namespace is under either Basic or Standard SKU. I wouldn't read into 2000 per second performance benchmark all that much because the actual throughput per second might vary on different factors (sessions, transactions, duplicate detection, average latency, message size, etc..) that might be unique to your needs and the resulting configuration.

For our official documentation on Partitioning, please review: Partitioned queues and topics
Please sign in to rate this answer.
Deepanshu Goyal 1 Reputation point

2022-02-23T04:31:32.077+00:00

Hello MikeUrnun, Thanks for your answer. I have following query.

On this link, it says otherwise that partitioning won't affect the TPS.
https://stackoverflow.com/questions/71221489/what-is-the-maximum-number-of-put-operation-allowed-in-partitioned-azure-service/71223282?noredirect=1#comment125899648_71223282

What are your thoughts on this?
In the end, we just want to know that how could we achieve 6000 messages (1KB) per second (TPS) in azure service bus?
Kindly help to suggest what should we use?
Basic, standard or premium tier? Or should we use partitioning too?

Thanks.

Mike Urnun 9,811 Reputation points Microsoft Employee

2022-03-01T21:48:27.97+00:00

Hello @Deepanshu Goyal - Sorry for the delay in my response. With Basic and Standards SKUs, there is indeed a throttling limit of 1000 operations per second as answered in the StackOverflow post that you referenced. Generally, you should be fine because the Service Bus SDK that you'll be using to send messages comes with built-in retry logic so that if a message is throttled, it'll get retried right away.

That said, If you have a hard requirement to overcome the 1000 operations per second limit, you'll want to switch to Premium SKU instead with which you can allocate more messaging units resource which then will help meet the high volume spike scenario. For more on this, please review: Throttling in Azure Service Bus Premium tier and feel free to let me know if any clarification is needed. You might give a read to the following blog post too: Premium Messaging: How fast is it?

Partitioning, on the other hand, comes especially helpful when you consider the passthrough time spent in Service Bus included in the calculation of the overall end-to-end TPS of your messages.

Mike Urnun 9,811 Reputation points Microsoft Employee

2022-03-04T02:15:29.123+00:00

@Deepanshu Goyal I hope the answers above bring you more complete clarity, let us know if you have any further questions.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Would Partitioning in Service Bus queue increase TPS?

1 answer

Your answer