-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use The_Comms_Arena in particle communication. #4175
Use The_Comms_Arena in particle communication. #4175
Conversation
Because
|
Maybe we can use |
Yes, that would require the least amount of changes. |
This is causing a memory overhead and performance overhead in ImpactX: ECP-WarpX/impactx#769 Let's discuss next week how we proceed (e.g., opt-in to this PR's features, changing defaults, etc.). |
For mesh data it is better to use a small, separate Arena for communication. But, we found that for particle communication this approach uses too much memory (see the ImpactX Issue here: ECP-WarpX/impactx#769) This restores the old default behavior (prior to PR #4175), but allows users to opt-in to using The_Comms_Arena if desired. The proposed changes: - [ ] fix a bug or incorrect behavior in AMReX - [ ] add new capabilities to AMReX - [ ] changes answers in the test suite to more than roundoff level - [ ] are likely to significantly affect the results of downstream AMReX users - [ ] include documentation in the code and/or rst files, if appropriate
The proposed changes: