search

rebus-org / Rebus.AzureServiceBus

:bus: Azure Service Bus transport for Rebus
https://mookid.dk/category/rebus
Other
33 stars 20 forks source link

Why are pre-fetching and retry features in client not used? #3

Closed trreeves closed 6 years ago

trreeves commented 6 years ago

The latest version of the Azure Service Bus client provides the following features, which are also implemented in the transport - was there a reason these have been implemented in the Transport and the client implementations not used?

mookid8000 commented 6 years ago

As mentioned here I once removed Rebus' own prefetching and replaced it by setting the PrefetchCount property on the input queue, but it didn't seem to improve the receive rate.

But as I also said, I might have done something wrong. Do you have any experience with this?

Regarding retries and error handling – Rebus uses its own error queues, mostly because this is the way it has always been. What do you think would be the benefit of using the native mechanism?

trreeves commented 6 years ago

Pre-fetching -> OK, fair enough. I haven't focused on consumers yet in my load testing. Retries -> Oh yeah, silly me! My Rebus lesson continues :-)

Thanks for the info.