... | ... | @@ -59,8 +59,8 @@ For the relationship between latency transit time and message size see [Communic |
|
|
# Message Size
|
|
|
The message size is used to refer to the size of messages in bytes used by Linktest to benchmark communication. For the relationship between latency transit time and message size see [Communication Time](#communication-time). Note that many communication APIs only support message sizes up to 2 GiB. For 32-bit MPI implementations the cumulative message size of all messages is restricted in total to less than 2 GiB.
|
|
|
|
|
|
# Mixing Task Ranks
|
|
|
Although by default Linktest tests the connection between a given task, which has a number associated with it called the rank, and all other tasks results may depend on the order in which the testing is performed. The `--mix` command-line option causes the task ranks to be randomly mixed which means that consecutive runs will test physical connections in a different order.
|
|
|
# Randomizing Testing Order
|
|
|
Although by default Linktest tests the connection between a given task and all other tasks, results may depend on the order in which the testing is performed. The `--randomize` command-line option causes the testing order to be randomly mixed which means that consecutive Linktest runs with this on will likely test physical connections in a different order.
|
|
|
|
|
|
# Number Of Messages
|
|
|
Linktest benchmarks communications by repeating a communication many times. The amount of times it repeats the sending of messages for timing purposes is controlled via the `--num-messages` command-line argument. This defines how many times the back-and-forth sending of messages is repeated for timing purposes. The final returned times are the average time it took the message to be sent back-and-forth.
|
... | ... | |