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.

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

BUG: benchmark mode should wait for all partitions in parallel #4491

Closed
mvashishtha opened this issue May 24, 2022 · 0 comments · Fixed by #4656
Closed

BUG: benchmark mode should wait for all partitions in parallel #4491

mvashishtha opened this issue May 24, 2022 · 0 comments · Fixed by #4656
Assignees
Labels
Benchmarking 🏁 Issues and pull requests for evaluating runtime bug 🦗 Something isn't working

Comments

@mvashishtha
Copy link
Collaborator

We are waiting for all partitions in sequence, but it's more accurate to wait for them all at once, e.g with ray.wait(partitions, num_returns=len(partitions)) for Ray. The performance difference is probably negligible because iterating across all the partitions should be really fast.

all(map(lambda partition: partition.wait() or True, partitions.flatten()))

@mvashishtha mvashishtha added bug 🦗 Something isn't working Benchmarking 🏁 Issues and pull requests for evaluating runtime labels May 24, 2022
@noloerino noloerino self-assigned this Jul 6, 2022
noloerino added a commit to noloerino/modin that referenced this issue Jul 12, 2022
…ark mode

Signed-off-by: Jonathan Shi <jhshi@ponder.io>
mvashishtha pushed a commit that referenced this issue Jul 15, 2022
* FIX-#4491: Wait for all partitions in parallel in benchmark mode

Signed-off-by: Jonathan Shi <jhshi@ponder.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Benchmarking 🏁 Issues and pull requests for evaluating runtime bug 🦗 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants