In my scenario I do only the basics: REGISTER/INVITE/sleep 45/BYE.
Running this scenario using the latest trunk (r599) of sipp consumes
100% cpu! This surprised me so much I went back to my old standby,
sipp-2.0.1, which consumes only 3% CPU on the same CentOS 5.7 host
with the same command line (below). I did appreciate the convenience
of sipp v3 printf-style inf files, but not enough to want to use 30x
the load generator boxes. Does anyone else have this trouble? The
command line is:
sipp proxy.xxx.com:5062 -aa -sf uac-ser-load.xml -r 100 -l 900 -t
tn -nd -trace_err -inf inf/userinfo.inf
Regards,
Ken
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
