Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better default for the RabbitMQ prefetch count #1

Closed
SimonCropp opened this issue Sep 16, 2013 · 1 comment
Closed

Better default for the RabbitMQ prefetch count #1

SimonCropp opened this issue Sep 16, 2013 · 1 comment
Milestone

Comments

@SimonCropp
Copy link
Contributor

Prefetch count is not defaulted to the same number of threads as the transport is configured to use. The old version defaulted to 1 which will have a negative impact on throughtput and put uneeded preassure on the broker by making it harder to find a free prefetch slot

@andreasohlund
Copy link
Member

We should also add doco/guidance on how to tune the prefetch count depending on how much latency can be tolerated

More here: https://groups.google.com/forum/#!msg/masstransit-discuss/-0F7jswXIso/k9dJynmhSR0J

@andreasohlund andreasohlund added this to the 2.1.0 milestone Feb 6, 2015
charlessolar added a commit to charlessolar/NServiceBus.RabbitMQNext that referenced this issue Oct 8, 2016
mixtura pushed a commit to mixtura/NServiceBus.RabbitMQ that referenced this issue Oct 11, 2019
[WIP] [MO20-1619] Added support of priority message property

Approved-by: kyrylo_korobov <kyrylo_korobov@epam.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants