... | ... | @@ -74,7 +74,17 @@ Ping-Pong tests are a standard tool for network operators. They can thought of a |
|
|
Ping-pong testing is useful to measure network latency and bandwidth. It is also less susceptible to differences in speed in a given direction since only the time it took for the message to go in both directions is recorded.
|
|
|
|
|
|
# Serial Testing
|
|
|
By default Linktest tests as many connections as possible in parallel, this, however, can cause tests to interfere. This is sometimes desired, for example, if real-world network performance under a sustained network load is to be tested. In other cases peak performance without the interference of other parallel tests is desired. In this case serial testing is done, in which each connection between a pair of tasks is tested individually. This effectively serializes the test and will cause it to take significantly longer. Serial testing can be turned on in Linktest by using the `--serial` command-line option.
|
|
|
By default Linktest tests as many connections as possible in parallel, this, however, can cause tests to interfere. This is sometimes desired, for example, if real-world network performance under a sustained network load is to be tested. In other cases peak performance without the interference of other parallel tests is desired. In this case serial testing is done, in which each connection between a pair of tasks is tested individually. This effectively serializes the test and will cause it to take significantly longer. Serial testing can be turned on in Linktest by using the `--serial-testing` command-line option.
|
|
|
|
|
|
# Serial Retesting
|
|
|
Some of the connections tested by Linktest will perform worse than others. By default Linktest retests some of the worst connections serially. This is to determine if the poor performance is due to conflicts with other parallel connections or other processes that run in parallel on the same node/CPU. If the times for a serially retested connection improves to expected values then that indicates that during the main measurement there was some type of conflict. It is a good indication that something might be wrong with a connection if said connection performance does not improve as expected after serial retesting.
|
|
|
|
|
|
The amount of connections to be serially retested can be controlled via the `--num-slowest` command-line argument followed by a positive integer indicating the number of worst connections to serial retest.
|
|
|
|
|
|
# Stress Testing
|
|
|
Linktest can be used to apply a nearly continuous connection load to stress a network. This is useful to see how stable a network remains under a continuous load.
|
|
|
|
|
|
Linktest can be configured to stress test using two command-line arguments. `--min-iterations` followed by a positive integer indicates how many times the main test of Linktest is at least repeated. `--min-runtime` followed by an integer indicates at least how long Linktest should repeat the main test. Linktest only stops repeating the main test if both are satisfied. If only one is specified then Linktest only tests against that one.
|
|
|
|
|
|
# Transit time
|
|
|
Transit time is the time it takes for an object to go from its origin to its destination. During this travel period the object is said to be in transit. For communication times, i.e. the time the message is in transit
|
... | ... | |