Reducing the number of time-step communications
Only active the ti_end comms for part and gpart if we are not running with limiters. When limiters are on, we do a second round of exchanges anyway.
This likely has a rather minimal effect but can help if we think the problem is that we swamped the MPI library. The better fix I am looking at next is to dramatically reduce the number of comms we do during the second round of exchanges.
Edited by Matthieu Schaller
Merge request reports
Activity
added MPI performance labels
requested review from @bvandenbroucke
added 101 commits
-
1be05292...48ecfdcd - 100 commits from branch
master
- 7cea3947 - Only active the ti_end comms for part and gpart if we are *not* running with...
-
1be05292...48ecfdcd - 100 commits from branch
added 1 commit
- 4330175c - Add a new task to do the collection of time-steps back to the top-level...
added 4 commits
-
4330175c...5ff17fe3 - 2 commits from branch
master
- 16c7d36d - Only active the ti_end comms for part and gpart if we are *not* running with...
- bf114747 - Add a new task to do the collection of time-steps back to the top-level...
-
4330175c...5ff17fe3 - 2 commits from branch
added 2 commits
added 1 commit
- 28d43e38 - Make engine_collect_end_of_step() only loop over local cell
Please register or sign in to reply