>> marek cervenka <[EMAIL PROTECTED]> writes: >> >>> hi, >>> >>> i'm testing asterisk 1.4/1.2 in the following scenario >>> centos5/cpu quad xeon E5335 2.0Ghz >>> - test clients behind nat >>> - 1500+ testing instances - reregister option from 1min to 1hour >>> - qualify set to 5000 >>> >>> top shows over 100% cpu. cpu cores sometimes go to 95% >>> with htop i see ~16threads but only one child have ~95% cpu >>> (how i can get info about that thread? what he is doing?) >>> >> oprofile can probably tell you. It can be a bit difficult to get >> all the debugging information into the right places so oprofile works, >> but it's very helpful. > > this is strace -p ppid_of_problematic_thread > > can you look if you see any anomalies?
one more info with iptables -A INPUT -p udp -s 0/0 -d 0/0 --dport 5060 -j REJECT cpu usage goes to 0-4% -> this problem is not some asterisk cpu deadlock but problem in process incoming packets --------------------------------------- Marek Cervenka ======================================= _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
