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.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

How can I generate 1 Gbit/s traffic for a webserver?

Votes:

0

Your Vote:

Up

Down

We need to generate more than 1Gbit/s traffic during a stress test using webserver stress tool.

Could you please advice, if there is the option to run stress testing from multiple testing servers? Or is there any possibility that we could generate such traffic with your tool?

general networking software stresstest traffic web-server webserver-stress-tool webstress

Created on Feb 11, 2010 9:48:43 AM by  Dirk Paessler [Founder Paessler AG] (10,932) 3 4

Last change on Feb 23, 2010 12:24:20 PM by  Daniel Zobel [Product Manager]



1 Reply

Accepted Answer

Votes:

1

Your Vote:

Up

Down

Well, creating a constant stream of 1Gbit/s from a webserver is an impressive task :-)

  • 1. You need a webserver (or a webserver farm with load balancer) that is able to deliver 1 Gbit/s.
  • 2. You need a network infrastructure (switches etc.) that is able to handle this load.
  • 3. You need one (or several) test clients running Webserver Stress Tool to create the necessary HTTP requests

In most cases one client will not be enough. But you can of course create any load using several copies of Webstress on several PCs.

It's almost impossible to say in advance how many instances/PCs you would need for a specific load - there are so many parameters that will influence this:

  • Number of URLs requested: make it as small as possible to avoid the lower bandwidth usage that occurs during the protocol/session handling phases of the HTTP requests
  • Average size of the requests: make it as large as possible (several hundred kilobytes) so that
  • Number of simulated users: Stay between 100 and 300 simulated users per Webstress instance (this avoids that threads have to wait for each other too much and maximizes the load generated by the webstress instance)
  • Clicktime ("think time") between clicks: Turn this to zero (as soon as one simulated user has finished one request, the next one is sent immediately)

The disadvantage of running several instances of webstress is that you can not consolidate the results into one big results set. You need to run external monitoring tools (like PRTG Network Monitor) to monitor the consolidated load and bandwidth.

More info about Webserver Stress Tool

Created on Feb 11, 2010 10:01:32 AM by  Dirk Paessler [Founder Paessler AG] (10,932) 3 4

Last change on Feb 16, 2010 3:55:19 PM 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.