For what it's worth... I also observed an unusually high level of CPU activity on my small (home-system) Asterisk installation, shortly after I switched to 1.6.2.13.
The pattern in my case was (as best as I could tell) a CPU load of 2% to 10%, pulsing upwards every few seconds. I couldn't resolve it any more finely than that, at the time I saw it. This is a very small Asterisk install (just two or three SIP extensions registered at the time, no calls in progress, no significant activity noted on the net interfaces at the time), running on an Atom N270 CPU system. I am using the "internal_timing = yes" option (pthreads timing rather than dahdi). I did a "core restart when convenient", Asterisk restarted, and the CPU load dropped to negligible levels. It has remained low ever since (about 7 minutes of CPU used, over the space of a couple of days). I have a hunch that in 1.6.2.13, some resource isn't being cleaned up properly after calls terminate or extensions de-register, and that the system is spending a significant amount of time "chasing its tail" navigating through these obsolete resources. Just a hunch, though... nothing to back this up. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
