Phase duration exceeded, but not all users were launched

Question

I've test socket with tsung.

tsung.xml:

<?xml version="1.0"?>
<!DOCTYPE tsung SYSTEM "/usr/local/share/tsung/tsung-1.0.dtd">
<tsung loglevel="notice" version="1.0">

  <!-- Client side setup -->
  <clients>
    <client host="localhost" use_controller_vm="true" maxusers="10000"/>
  </clients>

  <!-- Server side setup -->
<servers>
  <server host="127.0.0.1" port="5678" type="tcp"/>
</servers>

  <!-- to start os monitoring (cpu, network, memory). Use an erlang
  agent on the remote machine or SNMP. erlang is the default -->
  <!-- <monitoring>
    <monitor host="localhost"></monitor>
  </monitoring> -->

  <!-- <load duration="1" unit="minute" loop="3"> -->
  <load loop="3">
  <arrivalphase phase="1" duration="1" unit="minute">
    <!-- <users interarrival="0.001" unit="second"></users> -->
    <users arrivalrate="200" unit="second" />
  </arrivalphase>
 </load>
<!--
  <options>
   <option type="ts_http" name="user_agent">
    <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
    <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
   </option>
  </options>
 -->
  <!-- start a session for a http user. the probability is the
  frequency of this type os session. The sum of all session's
  probabilities must be 100 -->

 <sessions>
  <session probability="100" name="socket-example" type="ts_socket">
    <request>
      <socket></socket>
    </request>
  </session>
 </sessions>
</tsung>

And in almost every phase, I received report: Phase duration exceeded, but not all users were launched, just like folloing:

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
    ts_config_server:(5:<0.50.0>) All remote beams started, sync 

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
    ts_config_server:(5:<0.50.0>) New arrival phase 1 for client "localhost" (last ? true): will start 6000 users

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
    ts_config_server:(5:<0.50.0>) New arrival phase 2 for client "localhost" (last ? true): will start 6000 users

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
    ts_config_server:(5:<0.50.0>) New arrival phase 3 for client "localhost" (last ? true): will start 6000 users

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
    ts_config_server:(5:<0.50.0>) New arrival phase 4 for client "localhost" (last ? true): will start 6000 users

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
         ts_launcher:(5:<0.84.0>) Expected duration of first phase: 60.0 sec (6000 users) 

=INFO REPORT==== 21-Sep-2012::14:28:44 ===
         ts_launcher:(5:<0.84.0>) Activate launcher (6000 users) in 10019 msec 

=INFO REPORT==== 21-Sep-2012::14:29:54 ===
         ts_launcher:(5:<0.84.0>) Phase duration exceeded, but not all users were launched (440 users, 7.3% of phase)

Is there any problem?

Answer 1

Are you sure that's the tsung.xml associated with that log? It looks like you've only specified 1 phase while the log is showing 4...or does that loop recycle the 1st phase identically, 3 more times?

Not sure how familiar you are with Tsung, I just started using it a couple weeks ago and I've found it to be NO JOKE. Extremely powerful. I had to tune it way back because of how wickely it can scale, distribute and force multiply a load.

It looks like you've got it set kinda stout. It's late and my math's never been good but it looks like you're blasting 200,000 http get's a second for a minute. Go ahead and multiply 200,000 x 3 to get a bare minimum packets per second. Is that what your intent was?

What I did was bump it all the way down to 1 user arriving 1 time a second for 1 min to see if it would actaully stop on it's own and get a feeling for it's loading capabilities