Previous testing was done on Version 3.2.
I switched to Version 3.3 using the exact same setup "turning off all trace
options". The result in Version 3.3 is that I loose ~2000 calls (32000 calls,
600 calls per second).
If I slow the call rate down to 210 calls per second, I do get all calls
processed but I am confused why there isn't any indication as to what is
missing or why the calls get screwed up.
Tom Everett
From: Everett, Thomas A (Tom) [mailto:tom.ever...@alcatel-lucent.com]
Sent: Friday, November 01, 2013 1:29 PM
To: sipp-users@lists.sourceforge.net
Subject: Re: [Sipp-users] SIPP appears to stop for a brief period every ~30
seconds
I cannot reproduce the last call error where the client stays open so you'll
have to disregard that part of my last email.
From: Everett, Thomas A (Tom)
Sent: Friday, November 01, 2013 12:57 PM
To: Everett, Thomas A (Tom);
sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>
Subject: RE: [Sipp-users] SIPP appears to stop for a brief period every ~30
seconds
Problem resolved, at least for now.
Turns out the "rpciod/0" is writing log files based on "-trace" options. As
soon as I turned these off, I am now processing all 32000 calls without any
"stopped" display activity.
Might be nice to have some better throttling or control and/or messaging to
indicate these issues. Turning on trace activity should halt calls in favor or
corrupting calls and trace warnings should be issued if this is an unavoidable
condition.
I also noticed that although I am making 32000 calls (XML file has 32001 lines
with 1 line at the top defining "sequential") the server command terminates at
the end but the client command stays open.
When I leave the server "-m" option value at 32000 and change the client "-m"
option to 32001 then both commands terminate when 32000 calls are complete.
Is this a bug?
From: Everett, Thomas A (Tom) [mailto:tom.ever...@alcatel-lucent.com]
Sent: Friday, November 01, 2013 12:21 PM
To: sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>
Subject: Re: [Sipp-users] SIPP appears to stop for a brief period every ~30
seconds
Looked a bit at running tasks and what I see is that "rpciod/0" and "pdflush"
occur on the ~30 second intervals when SIPP is making calls.
I also find many complaints about "rpciod" for other reasons. Could this be my
problem?
Thanks,
Tom Everett
From: Everett, Thomas A (Tom) [mailto:tom.ever...@alcatel-lucent.com]
Sent: Friday, November 01, 2013 10:49 AM
To: sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>
Subject: [Sipp-users] SIPP appears to stop for a brief period every ~30 seconds
I am sending 32000 calls at 410 calls per second (tried 210, and 600 without
much difference) and as the client side is processing calls the output appears
to stop at approximately 30 seconds for what appears to be a random wait time.
I think the server side also has this "stop" state around the same 30 second
interval. When it restarts there is a huge gap between invites and
acknowledged calls. The result is that only about 20000 calls are completed.
Where do I start looking for the reason for this stop, and resulting limit to
the number of calls processed?
Thomas Everett
Alcatel-Lucent
1 Robbins Road
Westford, MA. 01886
1-978-952-7478
tom.ever...@alcatel-lucent.com<mailto:tom.ever...@alcatel-lucent.com>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
