<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tzafrir Cohen escribió:
<blockquote cite="mid:20090601145546.GU3227@xorcom.com" type="cite">
<pre wrap="">On Mon, Jun 01, 2009 at 09:23:48AM -0500, Miguel Molina wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
I just upgraded a production server to asterisk 1.4.25, compiling with
the following:
[*] 1. DONT_OPTIMIZE
[*] 2. DEBUG_CHANNEL_LOCKS
[*] 3. DEBUG_THREADS
[*] 4. DEBUG_FD_LEAKS
[ ] 5. LOW_MEMORY
[*] 6. MALLOC_DEBUG
[ ] 7. RADIO_RELAX
[ ] 8. STATIC_BUILD
[ ] 9. IAX_OLD_FIND
[*] 10. LOADABLE_MODULES
Do this options make asterisk consume much more CPU?
</pre>
</blockquote>
<pre wrap=""><!---->
DONT_OPTIMIZE sure does, for starters.
</pre>
</blockquote>
You were right. Almost one day with the server nearly overloaded (it's
a 24/7 call center) taught me the lesson: don't try to debug directly
on production machines, use instead a separate testing one with a copy
of the configuration if possible. Thanks to God for the spare CPU power
that was available. Never thought that disabling the optimizations were
going to impact the overall performance of asterisk that much.<br>
<br>
By the way, everything back to normal with no special compiler flags,
1.4.25 seems very stable, with the memory leak problem gone. Thanks a
lot asterisk developers!<br>
<br>
<pre class="moz-signature" cols="72">--
Ing. Miguel Molina
Grupo de Tecnología
Millenium Phone Center
</pre>
</body>
</html>