Jump to content
WAPT Forum

sergei

Administrators
  • Content Count

    718
  • Joined

  • Last visited

Posts posted by sergei


  1. 1. Does this "run until all users complete" launch all users immediately? Or does it stagger the number of sessions? The results I'm seeing seem to show all users running at once with a bunch timing out and then retrying, is this accurate?

     

    "Complete all open sessions" option means that after time of test is over all opened sessions should be executed to the end. A number of started users is regulated by "User Load" options.

     

    2. More importantly, this one is throwing me off. Using just the first (main) page of this test as an example, I see zeros in the report for the time frames 00:00-00:55 and through 00:55-01:50. What this tells me is that the server did not respond with any data during these times, right? Then in the 01:50-02:45 time frame I see an average response time of 78.4 seconds... How could the response time have been 78 seconds if it's within the 1:50 to 2:45 time frame? Am I reading this wrong?

     

    Average time is available only after whole request with all page elements was completed. Therefore you see results only in 1:50 - 2:45 time frame.

     


  2. The number of VUs that can be created during the test by each WAPT Pro load agent depends on several parameters including the hardware of agents systems, network capability and the tested server itself. For example, if typical response time is very short, the agent will have less time for preparing and sending subsequent requests. So, in this case each agent will create less simultaneous VUs. However this will also result in more user sessions executed during a time frame. What I am trying to say is that it is easier to create many simultaneous users for a slow site then for a fast one. Also, maximum number of concurrent VUs depends on the profiles that you use and the content of server responses. For example, a load agent will work more efficiently if typical server response is a short message, then if it is a 100kb HTML text.

     

    Overall the average number is about 1000 – 2000 VUs per load agent. By the way, if you want, you can purchase additional load agents separately, if you see that your current configuration is insufficient.

     

    WAPT works identically to WAPT Pro with a single load agent running on the same system.


  3. Regarding server utilisation reports is the bellow true to identify bottlnecks

     

    Processor\Processor Time \%. CPU activity in percentage.

    If this counter (divided by the number of processors) has a sustained value of five or more threads, there is a processor bottleneck.

     

    If server is optimized and multithreaded that CPU utilization must be 100% for a lack of CPU, I think.

     

    Physical disk\Disk Time \%.

    More than 55% for continuous periods indicates a bottleneck.

     

    WAPT monitors free disk space.


  4. Hi, George

     

    In the current version of WAPT you can initialize a variable by random value from an external file and use it as URL path. But the file should contain already formed URLs. In the next version of WAPT Pro you will be able to use java script and build URL path dynamically during a test.

     

×
×
  • Create New...