sys-cmd h1load

sys-cmd h1load sends requests with the specified number of concurrent connections to an HTTP/1 address from the route table selected in WEB-CLI and writes the request count, the errors and the response times line by line for every second during the test. It is used to follow how the load is served over time and at which moment the latency increases.

Command Summary

TR7 WEB-CLI · sys-cmd h1load

# type h1load and press Tab: a free parameter

admin@TR7LBWAF01> sys-cmd h1load

<h1load-parameter-1>

 

admin@TR7LBWAF01> sys-cmd h1load <parameters> <address>

admin@TR7LBWAF01>  

Everything written after the word h1load is passed to the tool as it is. There is no mandatory field; the address is written at the very end.

How It Works

Subject	Behavior
Context	The requests are sent from within the selected v-device and route table.
Duration	It closes when it reaches the request count or the duration limit; if a limit is not given, it is stopped with Ctrl+C.
Pipe	The output can be filtered with | or written to a file with to-file.
Recording	Every run is written to the user logs.

Frequently Used Parameters

Parameter	What it does	What is written after it
-c	Determines the number of concurrent connections	A number (e.g. 20)
-n	Determines the total number of requests to be sent	A number
-d	Determines the duration of the test	Seconds
-t	Determines the number of threads to be used	A number

The table summarizes the frequently used parameters; the parameter names and the output columns depend on the version of the tool on the device.

Examples

TR7 WEB-CLI · A) With 10 connections, 1000 requests

admin@TR7LBWAF01> sys-cmd h1load -c 10 -n 1000 http://10.0.7.20/

admin@TR7LBWAF01>  

TR7 WEB-CLI · B) For 30 seconds, 20 connections

admin@TR7LBWAF01> sys-cmd h1load -c 20 -d 30 http://10.0.7.20/

admin@TR7LBWAF01>  

Things to Know

The load affects real users

The test sends real requests to the target. On a live vService it is started with a low connection count and a short duration, and the values are increased step by step. WAF, rate limiting or connection limit rules can block the test traffic; in this case the measurement shows the behavior not of the target but of the rules.

• The side that generates the load is measured as well. Very high connection counts consume the device's own processor resources; in this case the result shows not the limit of the target but the limit of the load generator.
• If the total rate and the latency distribution are wanted as a single summary, wrk is used.