On Fri, Dec 15, 2017 at 02:35:14PM +0100, Olivier wrote:
> Hi,
>
> 2017-12-14 16:28 GMT+01:00 Tzafrir Cohen <[email protected]>:
> > > 2. Is correct to understand that to get DONT_OPTIMZE, BETTER_BACKTRACE
> > and
> > > so on options compiled in, I must recompile anyway ?
> >
> > Right. DONT_OPTIMZE has a considerable performance impact.
>
>
> How would you roughly evaluate this performance impact ?
> I don't want to CREATE issues with performance penalties but I think I
> can't afford to see Asterisk segfaults (a customer of mine has this with
> PJSIP) within having required data to open tickets.
DONT_OPTIMZE means building with hardly any compiler optimizations. Last
time I asked at #asterisk-dev they agreed with me it is not sensible to
ship such binaries.
> > I never
> > considered BETTER_BACKTRACE and its performance impact. Is it
> > independent of DONT_OPTIMZE?
> >
I just did. Indeed it seems to be independent. I fail to see any real
run-time impact of this if not explicitly used. I must have missed
something, as otherwise it would have been surely enabled by default.
What did I miss?
--
Tzafrir Cohen
+972-50-7952406 mailto:[email protected]
http://www.xorcom.com
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
