| ... | ... | @@ -14,6 +14,7 @@ This silent error message occurs when so many connections are to be tested that |
|
|
|
This error was produced using ParaStation MPI version 5.4.9-1.
|
|
|
|
|
|
|
|
At the time of writing three potential solutions exist:
|
|
|
|
1. Use a different MPI implementation like OpenMPI version 4.1.1.
|
|
|
|
2. Set the `PSP_UCP` environment variable to `2`. This is an undocumented option and it is unknown what it does. This may change in future ParaStation MPI versions. This option will cause ParaStation MPI to use UCP in the background.
|
|
|
|
3. Upgrade your communication hardware such that it has more memory and can support more connections. Depending on how many connections you want to test this may be enough. |
|
|
\ No newline at end of file |
|
|
|
1. Test using less tasks. Depending on your requirements this, however, may not be possible.
|
|
|
|
2. Use a different MPI implementation like OpenMPI version 4.1.1.
|
|
|
|
3. Set the `PSP_UCP` environment variable to `2`. This is an undocumented option and it is unknown what it does. This may change in future ParaStation MPI versions. This option will cause ParaStation MPI to use UCP in the background, same as if `PSP_UCP` is set to `1`. Setting `PSP_UCP` to `1`, however, causes MPI to perform differently to if `PSP_UCP` is set to `2` and will still cause the same error. If using this option you may encounter errors simillar or identical to the following: `ib_mlx5_dv.c:160 UCX ERROR mlx5dv_devx_obj_create(QP) failed, syndrome 0: Cannot allocate memory`. In this case you can either try testing with a different communication API or see 4.
|
|
|
|
4. Upgrade your communication hardware such that it has more memory and can support more connections. Depending on how many connections you want to test this may be enough. |
|
|
\ No newline at end of file |
