debug tips for cpu usage going wrong, deadlock issues, within pjsip or not. win32 specific thread profiling function used.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



After I read articles of pjsip performance and benchmark, I decided to use
long time real load test result to show we can build very high performacne
and reliable server side program on top of pjsip. And I select pjsip-ua api
to do test because pjsua/pjmedia will be limited by software based codec and
network traffic processing.
My test program was modified on top of pjsip-performance.Its design is quite
different with yours. What I prefer thread module is use the same number
theads as your cores.

SIP signal is handled by pjsip-ua api and RTP use external
hardware network chip to handle.

At that beginning, I were also facing deadlock issue.But almost was caused
by my misunderstanding of pjsip mutex locking design. After read the
sourecode and play with log file and gdb, I finally could complete this 72
hours load test.

I spent some time to read pjsua/pjmedia sources. I would say it is very nice
and very carefully when handling mutli-threaded and so much mutex.

regards,
Gang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090522/7c473f2a/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux