-
Notifications
You must be signed in to change notification settings - Fork 37
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
Specialization for handoffs preceeding non-monotone/blocking operators (perf optimization) #166
Labels
core api
hydroflow excepting the surface syntax
enhancement
New feature or request
performance
scheduler
Something with the scheduler (part of the Core API)
Comments
MingweiSamuel
changed the title
Non-monotone operators can have bespoke handoffs
Some non-monotone operators could have bespoke handoffs as an optimization
Aug 4, 2022
Another example: Sort is preceded by Handoff, but we could have a HeapHandoff or something that would do most of Sort, and save rebuffering. |
7 tasks
MingweiSamuel
changed the title
Some non-monotone operators could have bespoke handoffs as an optimization
Specialization for handoffs preceeding non-monotone/blocking operators (perf optimization)
Mar 16, 2023
MingweiSamuel
added
the
scheduler
Something with the scheduler (part of the Core API)
label
Apr 27, 2023
Required:
Future Optimization Rule:
|
jhellerstein
added
P2
Medium priority
and removed
P1
High priority
P2
Medium priority
labels
Jun 5, 2023
8 tasks
moved to #1500 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
core api
hydroflow excepting the surface syntax
enhancement
New feature or request
performance
scheduler
Something with the scheduler (part of the Core API)
For example, if we have max() or min(), a preceding handoff would only ever need to store a single max or min element, streaming. But currently we only have VecHandoffs, which store everything. So we can be more efficient. This will probably tie in to using lattice types in handoffs.
The text was updated successfully, but these errors were encountered: