Test scalapack/*: restrict all scalapack tests to less than 10 mpi ranks #15475
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Let us restrict the maximal concurrency of scalapack tests to less than 10 MPI ranks: - The purpose of these tests is to test our interfaces to scalapack and not whether scalapack functions properly for high(er) MPI concurrency. As such testing a few variants with a low number of MPI ranks is enough. - This cuts down the number of tests in our testsuite that have a concurrency of 10 or more from around 225 to around 190. The issue with these tests is the fact that we have to block off parallel slots in the ctest run equal to the number of MPI ranks. Meaning the more tests we have that have a high number of MPI ranks the less optimal the scheduling in ctest.
drwells
approved these changes
Jun 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let us restrict the maximal concurrency of scalapack tests to less than 10 MPI ranks:
The purpose of these tests is to test our interfaces to scalapack and not whether scalapack functions properly for high(er) MPI concurrency. As such testing a few variants with a low number of MPI ranks is enough.
This cuts down the number of tests in our testsuite that have a concurrency of 10 or more from around 225 to around 190. The issue with these tests is the fact that we have to block off parallel slots in the ctest run equal to the number of MPI ranks. Meaning the more tests we have that have a high number of MPI ranks the less optimal the scheduling in ctest.