What are the recommended parameters?

Choose parameters based on your testing goals. Start conservative and increase gradually to avoid overwhelming servers.

Use Cases #

Light Testing / Development #

Safe for development servers and small websites

• Connections: 1-5
• Duration: 10-30 seconds
• Pipelined: 1

Moderate Load Testing #

Suitable for staging environments and medium traffic sites

• Connections: 10-50
• Duration: 30-60 seconds
• Pipelined: 1-2

Heavy Load Testing #

For production stress testing. Monitor server resources carefully

• Connections: 50-200
• Duration: 60-300 seconds
• Pipelined: 2-5

Stress Testing / Capacity Planning #

Maximum load testing. Only use on dedicated test servers with monitoring

• Connections: 200-1000
• Duration: 300-1800 seconds
• Pipelined: 5-10

Best Practices #

1. Start with low values and gradually increase to find your server’s limits

2. Monitor server CPU, memory, and network usage during tests

3. Test during off-peak hours or on dedicated test environments

4. Use pipelined requests (2-5) to simulate real browser behavior

5. Higher concurrent connections create more load but may hit server limits

6. Longer durations (60+ seconds) provide more accurate average metrics