Hello,
i apologize for the late reply.
On Tuesday 23 March 2004 02:37, zeusng wrote:
Can anyone give me a realistic test case for measuring SER performance? I've been using sipsak to stress my SER server but am not able to interpret the result.
Sipsak is intended to stress your proxy, but not to mesaure the speed (CPS) of a proxy. There are simply to many unknown variables which can influence the results from sipsak.
Here are some sipsak were run:
[siptest@sipuat siptest]$ sipsak -U -I -e 10000 -s sip:40@mysip.test -r 5060 -n 800 -z -vv [siptest@sipuat siptest]$ sipsak -U -I -e 50000 -s sip:30@mysip.test -r 5060 -n 2 -z -vv [siptest@sipuat siptest]$ sipsak -U -I -e 10000 -s sip:40@mysip.test -r 5060 -n 150 -z -vv [siptest@sipuat siptest]$ sipsak -U -I -e 10000 -s sip:40@mysip.test -r 5060 -n 50 -z -vv
One of the result as follow:
All usrloc tests completed successful. received last message 109125.023 ms after first request (test duration).
This is simply the time from the first request send out the proxy till the last reply was received.
biggest delay between request and response was 46082.422 ms
As your allready noticed it is possible that under some circumstances your proxy do not answer very quickly (probably because it is blocked by something else). Because of this sipsak tries to mesarue the delay between the time when the request was send out and when the reply for this request was received. But it do not keep all the delays but only the biggest delay during the complete test run.
10 retransmission(s) received from server.
Sometimes you receive replys for requests multiple times. Mostly because the proxy answers stateless (e.g. the registrar) and the was a retransmissions of the initial requests because no reply was received untill 5000 ms. This counts simply how often sipsak received a retransmitted reply.
9 time(s) the timeout of 5000 ms exceeded and request was retransmitted.
9 times sipsak did not received a reply on its request after 5000 ms and retransmitted its request.
I guess a delay of 46s (46082.422ms) is definitely not acceptable. What should I set for -n to be comparable to real world traffic.
What is not acceptable for you depends a lot on your definitions ;-) But as i allready wrote sipsak is not intended to get any comparable messarument results. It should be fine to tests e.g. if your proxy runs faster with option X turn on or off. But allways remember to run such tests - in environments where no other actions/processes interfere with your test runs - to definitely exclude bottlenecks like network speed, CPU power, speed of used services like DNS
And what kind of result should I expect.
That depends too much on your environments. And the output is just a small help to ease your daily configuration work ;-)
Greetings Nils
Side issue:
During my stress test, I experience the same problem Andres reported last Nov. udp_rcv_loop:recvfrom:[11] Resource temporarily unavailable
After I modify some kernel (Fedora Core 1, Linux 2.4.22) parameters, the problem seems to go away. Anyone happy to prove the case?
# echo "8388608" > /proc/sys/net/core/rmem_max # echo "8388608" > /proc/sys/net/core/wmem_max # echo "8388608" > /proc/sys/net/core/rmem_default # echo "8388608" > /proc/sys/net/core/wmem_default
Zeus
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, you are prohibited from reading, copying, distributing and using the information. Please contact the sender immediately by return email and destroy the original message.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers