| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
I got the head revision a couple of months ago and ran a test app which created two stacks and made calls between them. This app was able to handle 372 calls/sec on Windows Server 2003 (32 bit) on a dual processor 2.8GHz Xeon machine with 2GB of RAM. Each call involved sending an INVITE from one instance of the stack to the other and then receiving a 180 and 200OK response and then sending an ACK followed by a BYE. So each call involved processing 10 SIP messages, hence you could say 3,720 SIP msgs per second. Test program is attached... -----Original Message----- From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Vishal K. Singh Sent: Friday, July 21, 2006 12:18 PM To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: [reSIProcate] resiprocate performance Hello Everyone, Has anyone done some performance measurements with resiprocate stack or repro proxy server ? It would be very helpful if you could share your performance results. How much is raw message processing capacity of the stack and of the DUM layer? I am trying decide whether to use the stack or DUM and performance trade-offs. Also, Is there any plan to change the DUM layer soon ? Thanks a lot for your time. Regards, Vishal _______________________________________________ resiprocate-devel mailing list resiprocate-devel@xxxxxxxxxxxxxxxxxxx https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
Attachment:
testSpeed.cpp
Description: testSpeed.cpp