<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 1/4/2022 5:49 PM, Joshua C. Colp
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAM0A2Z3BnGpq2w6J0iB==RzRfwtt9NDuvdQRqMui7J+gECGzBw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Tue, Jan 4, 2022 at 6:22 PM <<a
href="mailto:asterisk@phreaknet.org" moz-do-not-send="true"
class="moz-txt-link-freetext">asterisk@phreaknet.org</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">That's a really fair
point - maybe another potential source of improvement?<br>
<br>
I do use AMI for some things, but I have no use for the
"Newexten" and <br>
"Varset" AMI events (if I run my "amidump.php" script, I'll
see hundreds <br>
of these constantly even for a single call).<br>
<br>
In addition, it makes using core set debug >= 3 a real
pain, because <br>
then every complete AMI event is dumped, the result of which
is that 90% <br>
of the debug suddenly becomes an AMI dump of new exten and
new vars.<br>
</blockquote>
<div><br>
</div>
<div>Stasis events can be disabled in stasis.conf, I don't
know the ramifications of disabling new exten but varset is
fine. Generating the stasis events is what can be expensive.</div>
</div>
</div>
</blockquote>
<p>Thanks, I'll play around with disabling both of them and see how
much that helps.</p>
<p>I see "ast_channel_varset_type" in stasis.conf - which one would
be the right one for disabling Newexten? I poked around the code a
bit but I'm not following the connection as much.<br>
</p>
<blockquote type="cite"
cite="mid:CAM0A2Z3BnGpq2w6J0iB==RzRfwtt9NDuvdQRqMui7J+gECGzBw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>AMI less so, and AMI itself has functionality for
filtering events you don't want.</div>
</div>
</div>
</blockquote>
<p>That's true (and I do filter) but AMI itself is still processing
the event, so it'll mean a waterfall of AMI dumps with core set
debug >= 3, and perhaps the overhead is still significant for a
large dialplan.</p>
<p>Disabling these two AMI events in particular, entirely, would be
nice. It seems like disabling the stasis events might take care of
that:</p>
<p>; Use of this functionality may break more complex functionality
in Asterisk<br>
; such as CEL, CDR, transfers, etc. and will likely cause related
messages in ARI<br>
; and AMI to go missing.</p>
<p>I don't use ARI at all - or CEL - so as long as CDR remains
intact, I could probably shut off a few of these...<br>
</p>
<blockquote type="cite"
cite="mid:CAM0A2Z3BnGpq2w6J0iB==RzRfwtt9NDuvdQRqMui7J+gECGzBw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
Adding an option to disable generating those events could
probably help <br>
with that, and regardless of the performance benefit, would
make dealing <br>
with debug and AMI a lot easier. I wonder if disabling
snapshots would <br>
also help.<br>
</blockquote>
<div><br>
</div>
<div>Fair warning - things internally depend on snapshots.
Disabling them outright will likely break things.</div>
</div>
</div>
</blockquote>
Got it, I wasn't as sure about this. I'll probably leave snapshots
alone for now.<br>
<blockquote type="cite"
cite="mid:CAM0A2Z3BnGpq2w6J0iB==RzRfwtt9NDuvdQRqMui7J+gECGzBw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
Can you think of other things about dialplan which hurt
performance <br>
would could be similarly addressed?</blockquote>
</div>
</div>
</blockquote>
</body>
</html>