[asterisk-dev] [non]optimized builds

[Kurt Lidl]

Russell Bryant wrote:
> Michiel van Baak wrote:
>> On 08:56, Wed 06 Feb 08, Atis Lezdins wrote:
>>> Me too, and i actually keep DONT_OPTIMIZE enabled on production.
>>> Having optimization could be useful for some embedded devices, but
>>> generally people would want to know - if there's a crash - then why
>>> it's happening.
>> Same here.
>> I only disable (do not enable) DONT_OPTIMIZE on soekris
>> installs. most installs on server hardware run with
>> DONT_OPTIMIZE enabled.
> 
> But you guys are active in the development community.  The other 99.9%
> of the people that use Asterisk want it to perform as best it can (_with_
> optimizations) by default.  If it crashes for them, the debugging is to see if
> they can change what they are doing so it doesn't crash anymore, or find another
> version that doesn't crash.

My own personal experience is that compiled with -O6, asterisk crashes
under any sort of low loading. This was completely repeatable.

Merely changing the optimizations to -O2 yields a
binary that will run for one to two months before crashing.  This
is with Asterisk 1.2.27, on a pentium-4 cpu, running centos 4.5,
with a sangoma pri card, and about 45 SIP extensions, and half a
dozen IAX2 clients.

-Kurt