Give `+sbwt none` a try and measure how it affects your cluster. It
might reduce the idle CPU usage a bit. The only adverse effect it
might have is it might increase the latency of requests, but it's
something you can measure.
The `+S ${SCHEDULERS}` is how you'd explicitly specify how many
Thank you very much Nick for the reply.
Most appreciated.
1) I checked _active_tasks and it return empty array []
2) About +sbwt, we are running on physical hardware ... no container.
+sbwt none
+S ${SCHEDULERS}
Would the above config changes you suggested earlier have any adverse
effect?
Hi Alfred,
It could be you're seeing the effect of busy waiting from Erlang VM
schedulers. Erlang VM would spawn a scheduler for each CPU core, and
then after any of those schedulers run out of work, they would still
spin in a busy loop for a bit waiting for more work. Sometimes that is
not
