Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Eager distributed: Do not wait for completion in sequence #138

Closed
inducer opened this issue Jul 5, 2021 · 1 comment
Closed

Eager distributed: Do not wait for completion in sequence #138

inducer opened this issue Jul 5, 2021 · 1 comment
Labels
distributed Relating to distributed-memory support

Comments

@inducer
Copy link
Owner

inducer commented Jul 5, 2021

Right now, sends are posted and then receives are waited for in an arbitrary order. I don't know how big an impact this has, but using waitall or waitsome might be beneficial.

grudge/grudge/trace_pair.py

Line 328 in 1c44c4b

return [rbcomm.finish() for rbcomm in rbcomms]

@inducer inducer added the distributed Relating to distributed-memory support label Jul 5, 2021
@inducer
Copy link
Owner Author

inducer commented Jul 5, 2021

Duplicate of #40.

@inducer inducer closed this as completed Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
distributed Relating to distributed-memory support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@inducer