What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

How to I achieve maximum HTTP requests/second with Webserver Stress Tool?

Votes:

0

Your Vote:

Up

Down

I want to generate the maximum number of HTTP requests per second possible.

howto http webserver-stress-tool

Created on Feb 24, 2010 9:02:16 AM by  Daniel Zobel [Product Manager]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Achieving maximum HTTP requests per second with Webserver Stress Tool

In order to generate a maximum number of HTTP requests per second you should look at the following tips:

  • Webstress heavily relies on multithreading. Using a system with multiple processors and/or multicore CPUs helps a lot.
  • Memory should not be any issue with 1 GB RAM or more
  • Remove network bottlenecks: Use a fast network (Gigabit or more), fast switches etc.
  • Connect the machine running Webstress to the same switch as the server to be tested
  • Run a TIME based test (CLICKS based may also be ok)
  • Use a few hundred users (e.g. running with 200-500 users has shown good results). Running with 1000 users or more may decrease performance due to increasing thread synchronization overhead, because each "user" is simulated by its own thread
  • Set Click Delay to 0 seconds (this causes Webstress to send the next request immediately after the previous one has finished)
  • Use simple URL sequences (complex URL scripts can waste a lot of CPU power)
  • Disable HTML parsing (i.e. disable download of images, frames, objects etc.)
  • Disable saving of HTM files to the disk and disable the link checker
  • If you can live without it: disabling Detailed Logging and Request Log also pushes performance
  • Do not use a proxy (proxies should never be used with Webstress)

Finally, if all this does not give you enough testing power you may want to consider multiple systems running Webstress concurrently. The disadvantage is that you will not get aggregated test results though.

Created on Feb 24, 2010 9:02:29 AM by  Daniel Zobel [Product Manager]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.