Menu
As per this article: https://azure.microsoft.com/en..., Service Bus can process upto 2000 messages per second per 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 by the performance of a single message broker or messaging store.' If we create a partitioned queue/topic, I believe it creates 16 partitions internally. My question is: Does the throughput of a partitioned queue/topic rise linearly to 16 x 2000 = 32,000 (approximate) ? Or does the throughput of 2000 msg/sec remain. Can you please point me to any throughput benchmark for partitioned queue/topic? We are currently analyzing a scenario that needs a very high throughput topic. Guidance on this question will be really helpful.
This question has been posted on the Azure site also, at: https://azure.microsoft.com/en-us/documentation/articles/service-bus-performance-improvements/
819
As per this article: https://azure.microsoft.com/en..., Service Bus can process upto 2000 messages per second per queue/topic.
Service Bus queues support a maximum message size of 256 KB (the header, which includes the standard and custom application properties, can have a maximum size of 64 KB). There is no limit on the number of messages held in a queue but there is a cap on the total size of the messages held by a queue.
Scaling based on the number of messages in an Azure Service Bus queue. One of the most notable advantages of the Cloud is the ability to scale resources to meet demand. We then scale out or up when the demand increases, and we scale in or down when the demand decreases.
Service Bus messaging services (queues and topics/subscriptions) allow application to send messages of size up to 256 KB (standard tier) or 100 MB (premium tier).
Performance will vary based on a number of things. For example, many advanced features (like duplicate detection, sessions, transactions, etc,) will add overhead therefore decreasing throughput. In case you want to benchmark this yourself, try running this performance sample: https://github.com/Azure-Samples/service-bus-dotnet-messaging-performance
Also, because basic/standard are shared tenant models the performance you get today, may be different from the performance you get tomorrow. In addition you may not see linear scale as some nodes can be more busy than others.
For true predictability, premium is your best bet.
165
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
