Bumping this so it doesn’t get closed.
This seems to be a major issue with a basic function of a PBX: ringing queue members.
CPU load spikes dramatically at the exact moment that the PBX is trying to ring about 50 queue members (load is almost the same when ringing only 25 extensions), as can be seen in the screenshot below.
Also swap gets used up after about 3 weeks of uptime, indicating to me a potential problem with memory usage generated by the dialplan (system in the screenshot has 128GB of memory).
All of my v4 systems are experiencing this issue and the only workaround that I found was manually removing the queue-hints from the extensions__25_-hints.conf file and reloading the dialplan (used it only for testing, not for production because I don’t yet grasp all of the implications of removing them).
A system restart or Asterisk “core restart” lessens the effect for a couple of days, but then it comes back.
v3 systems do not have this issue regardless of how many extensions are rang at the same time.
Kudos @Vitor_Hugo_Costa for finding this!