
By default erlang VM determines a number of scheduler threads equal to a number of CPU cores it detects [0]. Running rabbitmq in container makes Erlang VM to think it has all host CPU power, making extra scheduler threads competing for CPU time and, depending on a difference between a number host CPU cores and container limits, causing CPU throttling even while idle. This commit limits a number of schedulers to a value actually available to container via k8s resource limits (min 1) emulating the default behavior. [0] https://www.rabbitmq.com/runtime.html#scheduling Change-Id: If36f63173de4c8035daf7aac4014c027c579b58f
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on freenode
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.
Description