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.

Sign up for GitHub

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

Jump to bottom

Use available processor number for default thread count in consumer work service #730

Closed
acogoluegnes opened this issue Mar 29, 2022 · 1 comment · Fixed by #731
Closed

Use available processor number for default thread count in consumer work service #730

acogoluegnes opened this issue Mar 29, 2022 · 1 comment · Fixed by #731
Assignees
@acogoluegnes
Labels
usability
Milestone
5.15.0

Comments

@acogoluegnes
Copy link
Contributor

The current value is Runtime#availableProcessors() x 2, but it was set a long time ago and is quite high now considering the number of cores available nowadays.

Setting the value to Runtime#availableProcessors() should be reasonable for most workloads.
@acogoluegnes acogoluegnes added this to the 5.15.0 milestone Mar 29, 2022
@acogoluegnes
Copy link
Contributor Author

Original mailing list post: https://groups.google.com/g/rabbitmq-users/c/q-FQ4xCIEnU/m/4LcaRg8_AwAJ.

@acogoluegnes acogoluegnes self-assigned this Mar 30, 2022
acogoluegnes added a commit that referenced this issue Mar 30, 2022
@acogoluegnes
Use available processor number for default thread count in consumer w…
49c5e2c 
…ork service

The current value is available processors times 2, which may be overkill
nowadays. The commit also allows using the rabbitmq.amqp.client.availableProcessors
system property value, which is convenient as it's configuration-based (no code
changes required).

Fixes #730
@acogoluegnes acogoluegnes mentioned this issue Mar 30, 2022
Merged
acogoluegnes added a commit that referenced this issue Mar 30, 2022
@acogoluegnes
Use available processor number for default thread count in consumer w…
659c21f 
…ork service

The current value is available processors times 2, which may be overkill
nowadays. The commit also allows using the rabbitmq.amqp.client.availableProcessors
system property value, which is convenient as it's configuration-based (no code
changes required).

Fixes #730

(cherry picked from commit 49c5e2c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acogoluegnes acogoluegnes

Labels
usability
Projects
None yet
Milestone
5.15.0
1 participant
@acogoluegnes