On Wed, Jan 5, 2022 at 9:28 AM <aster...@phreaknet.org> wrote: > On 1/5/2022 5:35 AM, Nikša Baldun wrote: > > Again, sorry for veering off topic. I'll just say that I have tried > modifiying Asterisk source. Disabling AMI events helps only a little, and > disabling Newexten alltogether proved too difficult, at least for someone > with limited insight into inner workings of Asterisk. > > I'll take a closer look at this at some point. Based on what Josh and you > have confirmed, it will be more difficult to decouple the Newexten event, > but just because this is the way it is now doesn't mean it has to stay that > way. Surely there is a way to turn it off (besides brute force commenting > code out), even if it requires some mucking around, and doing so would have > tangible benefits it sounds like. >
It may or may not. Stopping the Newexten event may provide little to no change, because it may not be the source of what is using CPU. The only way to truly know is to experiment, profile, and understand things as a whole. -- Joshua C. Colp Asterisk Technical Lead Sangoma Technologies Check us out at www.sangoma.com and www.asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
