Bruno Van Den Bossche wrote:
> Hallo all,
>
> As we recently took up some SIP-performance testing again and since our
> tests in the past the -trace_rtt option was added, we compared the
> measurement results obtained using three different methods:
>
> -trace_stat option which prints out global statistics about all calls.
> -trace_rtt which prints out more detailed statistics about each
> individual call
> - a network capture using Wireshark
>
> Our test-setup was the following:
> - switched network
> - dual core intel machines running at 2.8Ghz
> - Read Hat Linux Enterprise Edition installed
> - a call rate of 100 caps, 2 SIPp's directly communicating, UDP
> - a slightly modified uac and uas scenario: actually the scenario's are
> the default, but we increased the response-time repartition and
> call-lenght repartition granularity to 1 ms
> (<ResponseTimeRepartition value="1,2,3,4,5,6,7,8,9,10,11,12,...,300/>)
>
> The measured results are as follows:
> trace_stat:
>       <1 : 19606
>       <2 : 2559
>       <3 : 1
>       <4 : 1
>       (average: 0.615)
>               [ (19606*0.5 + 2559*1.5 + 2.5 + 3.5)/22167]
>
> trace_rtt:
>       <1 : 0
>       <2 : 6948
>       <3 : 15207
>       <4 : 10
>       <5 : 1
>       <6 : 1
>       average: 2.187
>
> pcap:
>       <1 : 22043
>       <2 : 3
>       <3 : 10
>       <4 : 111
>       average: 0.729
>
> So we notice a very big difference between the output of -trace_stat and
> -trace_rtt.  The output from the Wireshark trace and -trace_stat seems
> to be more in line.  Especially considering there is already some
> processing done by the time SIPp gets its hands on the packet.
>
> Is this an expected result?  The difference between the -trace_rtt
> output and trace_stat seems very large.  Although I initially expected
> that the trace_rtt output would allow us to get more detailed diagnostic
> results.
>
> Another odd result is that although Wireshark reports 111 messages to
> arrive later than 3ms, nor trace_rtt nor -trace_stat seem to detect this.
>
> Has anyone else noticed this behavior? And is it to be expected or do
> you think it can be fixed?
>
>
> Kind Regards,
> Bruno
>
>   
Hello Bruno,

I agree with you, trace-stat and trace-rtt should provide the same 
results. We'll look into that.
Now, in terms of accuracy, I would expect SIPp to be far more precise 
since the latest additions from Charles Wright. But I didn't had the 
opportunity to check myself. Which SIPp version are you using?

-- 
Olivier
HP OpenCall Software
http://www.hp.com/go/opencall/


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to