perf: Avoid multiple serialization #287
Merged
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
- We send the mesh to the neighbourhood with boost::send calls - But currently, this boost::send serialize the meach for **each** send, even if it is always the same mesh. - But we can serialize the mesh once and send the buffer. - It is only tested on advection-2d, with a performance gain
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.
Description
boost::sendcallsboost::sendserialize the mesh for each send, even if it is always the same mesh.Related issue
Performance issue when using MPI
How has this been tested?
It has been tested on the advection-2d test case
Code of Conduct
By submitting this PR, you agree to follow our Code of Conduct