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

Activate only by channel ID #526

Merged
merged 3 commits into from
Feb 5, 2024

Conversation

antiguru
Copy link
Member

@antiguru antiguru commented Jun 4, 2023

This changes activation to avoid an associated event, which is currently not used anymore. It also switches to a Vec to contain the activations, and deduplicates before activating operators.

This improves performance in edge cases:

➜  timely-dataflow git:(activation_no_event) time taskset 1 target/release/examples/pingpong $((2**20)) 64
taskset 1 target/release/examples/pingpong $((2**20)) 64  3.63s user 0.00s system 99% cpu 3.638 total
➜  timely-dataflow-master git:(master) time taskset 1 target/release/examples/pingpong $((2**20)) 64
taskset 1 target/release/examples/pingpong $((2**20)) 64  3.32s user 0.78s system 99% cpu 4.106 total

@@ -2,7 +2,6 @@

use std::rc::Rc;
use std::cell::RefCell;
use std::collections::VecDeque;

use crate::{Push, Pull};
use crate::allocator::Event;
Copy link
Member Author

Choose a reason for hiding this comment

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

Check if Event still needs to exist.

for (channel, _event) in borrow.drain(..) {
borrow.sort_unstable();
borrow.dedup();
for channel in borrow.drain(..) {
// TODO: Pay more attent to `_event`.
Copy link
Member Author

Choose a reason for hiding this comment

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

Update comment.

Signed-off-by: Moritz Hoffmann <[email protected]>
Signed-off-by: Moritz Hoffmann <[email protected]>
Signed-off-by: Moritz Hoffmann <[email protected]>
Copy link
Member

@frankmcsherry frankmcsherry left a comment

Choose a reason for hiding this comment

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

This makes sense to me, and we've left the comment in that reminds us how it might be different in the future (tracking the emptiness of channels, and not scheduling only on the basis of a message both sent and received).

@frankmcsherry frankmcsherry merged commit b869dcb into TimelyDataflow:master Feb 5, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants