And removed version of the code is actually harmful, as it's using
physicalprocessorcount (i.e. number of CPU sockets) for
calculations. So on a 2 CPU/48 thread system there it was 30 threads
instead of 768 calculated upstream.
I've decided that it's easier to completely remove this code instead
of duplicating current formula in upstream and providing a way to
override this value through hiera - just not worth a hassle.
Reviewed: https:/ /review. openstack. org/396686 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=2858871ff02 b0637e5df9e17ce 26f8217cf38071
Committed: https:/
Submitter: Jenkins
Branch: stable/7.0
commit 2858871ff02b063 7e5df9e17ce26f8 217cf38071
Author: Alexey Lebedeff <email address hidden>
Date: Fri Nov 11 19:20:23 2016 +0300
Remove erlang/rabbit thread pool calculation
Proper version of this calculation is implemented upstream - /github. com/rabbitmq/ rabbitmq- server/ issues/ 151
https:/
And removed version of the code is actually harmful, as it's using cessorcount (i.e. number of CPU sockets) for
physicalpro
calculations. So on a 2 CPU/48 thread system there it was 30 threads
instead of 768 calculated upstream.
I've decided that it's easier to completely remove this code instead
of duplicating current formula in upstream and providing a way to
override this value through hiera - just not worth a hassle.
Change-Id: I415d446af0a822 d2a5ce3478fd9db 1dd0f13e115
Closes-Bug: 1573696