... | ... | @@ -51,27 +51,44 @@ where `<<<VERSION>>>` is the three part version of Linktest executable. Like the |
|
|
|
|
|
`-m` or `--mode`: Specifies that the following ASCII string indicates the communication API to use for testing. Alternatively the communication API can be extracted from the extension of the Linktest executable name or from the `LINKTEST_VCLUSTER_IMPL` environment variable. When multiple ways of specifying the communication API are used then `-m` or `--mode` supersedes the linktest executable extension, which in turn also supersedes the `LINKTEST_VCLUSTER_IMPL` environment variable.
|
|
|
|
|
|
`--all-to-all`: Specifies that the following integer, if non-zero, indicates that all-to-all testing should be done before and after the main Linktest test if the used communication API is MPI.
|
|
|
`-o` or `--output`: Specifies that the following string indicates the filename of the output SION file.
|
|
|
|
|
|
`--bidirectional`: Specifies that the following integer, if non-zero, indicates that testing should occur bidirectionally instead of semi-directionally, which is the default.
|
|
|
`--num-slowest`: Specifies that the following integer indicates the number of slowest connections to serially retest after the end of the main test.
|
|
|
|
|
|
`--bisection`: Specifies that the following integer, if non-zero, indicates that the tasks for testing should be split in two halves and that testing should only occur between these two. This is useful for determining bisection bandwidths.
|
|
|
`--min-iterations`: Specifies that the following integer indicates the number of times the linktest benchmark should be repeated. If not one the writing of SION files is disabled. This command-line argument is useful to apply a communication load to the system.
|
|
|
|
|
|
`--randomize`: Specifies that the following integer, if non-zero, indicates that the order in which tests are performed is to be randomized.
|
|
|
`--min-runtime`: Specifies that the following floating-point--precision number indicates the number of seconds that Linktest should repeat itself for. If non-zero the writing of SION files is disabled. This command-line is useful to apply a communication load to the system.
|
|
|
|
|
|
`--serial-tests`: Specifies that the following integer, if non-zero, indicates that connections should be tested in serial. By default testing occurs in parallel.
|
|
|
`--memory_buffer_allocator`: Specifies that the following string indicates the memory buffer allocator type to be used for allocating the memory buffers for sending and receiving data. The following options are permitted:
|
|
|
|
|
|
`--no-sion-file`: Specifies that the following integer, if non-zero, indicates that the collected results should not be written out into a SION file.
|
|
|
| `memory_buffer_allocator` | Description |
|
|
|
| ------------------------- | ----------- |
|
|
|
| `DEFAULT` | The default allocator, either the `POSIX_aligned-memory_allocator`, if possible, otherwise the `aligned-memory_allocator` or the `CUDA_memory_allocator` if testing the CUDA API. |
|
|
|
| `aligned-memory_allocator` | Uses `aligned_alloc` to allocate buffers on a page boundary. |
|
|
|
| `pinned-memory-map_allocator` | Uses `mmap` to allocate buffers on a page boundary. |
|
|
|
| `POSIX_aligned-memory_allocator` | Uses `posix_memalign` to allocate buffers on a page boundary. |
|
|
|
| `CUDA_memory_allocator` | Uses CUDA `memalloc` to allocate memory on the GPU. |
|
|
|
|
|
|
`--parallel-sion-file`: Specifies that the following integer, if non-zero, indicates that the collected results should be written out into a SION file in parallel if writing is enabled.
|
|
|
|
|
|
`--num-slowest`: Specifies that the following integer indicates the number of slowest connections to serially retest after the end of the main test.
|
|
|
`--all-to-all`: Specifies that all-to-all testing should be done before and after the main Linktest test if the used communication API is MPI.
|
|
|
|
|
|
`--min-iterations`: Specifies that the following integer indicates the number of times the linktest benchmark should be repeated. If not one the writing of SION files is disabled. This command-line argument is useful to apply a communication load to the system.
|
|
|
`--bidirectional`: Specifies that testing should occur bidirectionally instead of semi-directionally, which is the default.
|
|
|
|
|
|
`--min-runtime`: Specifies that the following floating-point--precision number indicates the number of seconds that Linktest should repeat itself for. If non-zero the writing of SION files is disabled. This command-line is useful to apply a communication load to the system.
|
|
|
`--unidirectional`: Specifies that testing should occur unidirectionally instead of semi-directionally, which is the default. Cannot be used in conjunction with `--bidirectional`.
|
|
|
|
|
|
`-o` or `--output`: Specifies that the following string indicates the filename of the output SION file.
|
|
|
`--bisection`: Specifies that the tasks for testing should be split in two halves and that testing should only occur between these two. This is useful for determining bisection bandwidths.
|
|
|
|
|
|
`--randomize`: Specifies that the order in which tests are performed is to be randomized.
|
|
|
|
|
|
`--serial-tests`: Specifies that connections should be tested in serial. By default testing occurs in parallel.
|
|
|
|
|
|
`--no-sion-file`: Specifies that the collected results should not be written out into a SION file.
|
|
|
|
|
|
`--parallel-sion-file`: Specifies that the collected results should be written out into a SION file in parallel if writing is enabled.
|
|
|
|
|
|
`--randomize-buffers`: Specifies that the buffers should be randomized before sending and receiving. Randomization is done using the Mersenne Twister 19937 algorithm, which has a period of 2^19937-1.
|
|
|
|
|
|
`--mt_seed`: Specifies that the following integer is to be used as a seed for buffer randomization. This option is only important if `--randomize-buffers` is specified. The seed value can be between 1 and 2^32-1.
|
|
|
|
|
|
The arguments num-warmup-messages, num-messages & size-messages are required. The transport layer is usually given through the --mode option. In rare cases where this doesn't work, you can fall back to the linktest.LAYER executables, and/or set the environment variable `LINKTEST_VCLUSTER_IMPL`.
|
|
|
|
... | ... | |