8000 Call Operator::run from OperatorExecutor to remove busy-looping by pschafhalter · Pull Request #103 · erdos-project/erdos · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Call Operator::run from OperatorExecutor to remove busy-looping #103

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
Merged
merged 2 commits into from
Mar 25, 2020
Merged

Call Operator::run from OperatorExecutor to remove busy-looping #103

merged 2 commits into from
Mar 25, 2020

Conversation

pschafhalter
Copy link
Member

OperatorExecutors now call Operator::run from an async context. This allows waiting on the RunOperator signal using a blocking call instead of busy-looping.

Also fixes some bugs in the tests.

Fixes #102.

sukritkalra
sukritkalra approved these changes Mar 25, 2020
View reviewed changes
Copy link
Collaborator
@sukritkalra sukritkalra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Minor API things.

@pschafhalter pschafhalter merged commit 7660a39 into erdos-project:master Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sukritkalra sukritkalra sukritkalra approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Rust] Number of operators per node is limited by Tokio thread pool size
2 participants
@pschafhalter @sukritkalra
0