trixi-framework / trixi-framework/Trixi.jl
Potential performance impact from saving MPI rank during save solution callback
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 731
- Forks
- 167
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 25
Description
In https://github.com/trixi-framework/Trixi.jl/pull/2132, the MPI rank was included in `element_variables` during each call to the save solution callback for parallel simulations. It would be nice to evaluate whether this change impacts performance, and if that is the case, then introduce an option to deactivate or manually enable this functionality.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #2132 and the save solution callback, focusing on how MPI rank is added to element_variables during parallel saves. Benchmark the callback with and without rank saving in representative parallel simulations. Done means the performance impact is documented and, if material, an option is defined to deactivate or manually enable the functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- distributed-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100