Details
Description
Even in 1.8.1 we're using some 3-5 percent of CPU with single bucket when idle. For stats gathering, heartbeats etc.
We've spotted that current 2.0 is eating 15 or more.
Early evidence suggests that it's related to lots of erlang scheduler threads we're using now.