Azure ServiceBus queue

Question

Azure ServiceBus queue

K S Devadoss, Vishnu Kumar 20

In the Microsoft document states that regarding the PrefetchCount property with 2 different things to set the values. Both the recommendation are 2 different extreme.

Prefetching and ReceiveMessagesAsync

Prefetch can be up to n/3 times the number of messages processed per second, where n is the default lock duration.

High-throughput queue
Set the prefetch count to 20 times the maximum processing rates of all receivers of a factory. This count reduces the number of Service Bus client protocol transmissions.

Which one is to consider in my scenario,

Say I have a 5 receivers. Each could process 132 messages per minute.
I have setting with AutoCompleteMessages is false, ReceiveMode is PeekLock and MaxConcurrentCalls is 50.

From first recommendation my PrefetchCount is
n/3 = 30/3 = 10 //n is default auto lock duration

From second recommendation my PrefetchCount is
"20 times the maximum processing rates of all receivers of a factory"

20 * 132 * 5 = 13200/Min = 220/sec

5 is the receiver

132 is each receiver processing rate /min

Note: There is no batch message published.

MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-12-20T15:58:15.49+00:00

K S Devadoss, Vishnu Kumar Thanks for posting your question in Microsoft Q&A. In a normal scenario, you can use PrefetchCount is 20 times the maximum processing rates of all receivers of the factory.

Which means with default lock duration of 60 seconds, you can consider using 20 * 5 (receivers) * 2 (closest processing per second) = 200 as PrefetchCount. The same has been described in Prefetching doc as below:

If in case of using Prefetching and ReceiveMessagesAsync together, the math is 60 (default lock duration)/3 * number of messages processed per second (i.e. 10 = 5 receivers * 2 messages per second) which also implies the similar math as above.

I hope this clarifies and helps with your questions. If you have any other questions, let me know.
K S Devadoss, Vishnu Kumar 20 Reputation points

2023-12-20T18:24:53.7366667+00:00

Thanks @ MuthuKumaran for the swift response. I did not catch that when you say normal scenario. I use a ServiceBusProcessor to receive a message In . net client. And I also read inline with similar case in Java world. https://github.com/Azure/azure-sdk-for-java/issues/30483 Is this kind of behaviour applicable in .net as well?
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-12-20T19:23:14.98+00:00

K S Devadoss, Vishnu Kumar Sorry I meant in most cases. This specific issue is related to Java SDK and was addressed in the beta version. If you face any issues with .NET SDK, please let me know or feel free to open a new issue in the repo.

Your answer

MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-12-20T15:58:15.49+00:00

K S Devadoss, Vishnu Kumar Thanks for posting your question in Microsoft Q&A. In a normal scenario, you can use PrefetchCount is 20 times the maximum processing rates of all receivers of the factory.

Which means with default lock duration of 60 seconds, you can consider using 20 * 5 (receivers) * 2 (closest processing per second) = 200 as PrefetchCount. The same has been described in Prefetching doc as below:

If in case of using Prefetching and ReceiveMessagesAsync together, the math is 60 (default lock duration)/3 * number of messages processed per second (i.e. 10 = 5 receivers * 2 messages per second) which also implies the similar math as above.

I hope this clarifies and helps with your questions. If you have any other questions, let me know.
K S Devadoss, Vishnu Kumar 20 Reputation points

2023-12-20T18:24:53.7366667+00:00

Thanks @ MuthuKumaran for the swift response. I did not catch that when you say normal scenario. I use a ServiceBusProcessor to receive a message In . net client. And I also read inline with similar case in Java world. https://github.com/Azure/azure-sdk-for-java/issues/30483 Is this kind of behaviour applicable in .net as well?
MuthuKumaranMurugaachari-MSFT 22,446 Reputation points Moderator

2023-12-20T19:23:14.98+00:00

K S Devadoss, Vishnu Kumar Sorry I meant in most cases. This specific issue is related to Java SDK and was addressed in the beta version. If you face any issues with .NET SDK, please let me know or feel free to open a new issue in the repo.

Share via

Azure ServiceBus queue

Your answer