POC: Fusing repart and partial aggr #12526
Draft
+902
−120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rachelint
changed the title
… partitioned outputs.
Rachelint
force-pushed
the
fusing-repart-and-partial-poc
branch
from
7214b3e to
f81b292
Compare
Rachelint
force-pushed
the
fusing-repart-and-partial-poc
branch
from
f81b292 to
4108065
Compare
Rachelint
force-pushed
the
fusing-repart-and-partial-poc
branch
from
986ba1a to
05f4a49
Compare
This was referenced Sep 21, 2024
Rachelint
force-pushed
the
fusing-repart-and-partial-poc
branch
from
11230ac to
4d6f5e6
Compare
|
Thank you for your contribution. Unfortunately, this pull request is stale because it has been open 60 days with no activity. Please remove the stale label or comment or this will be closed in 7 days. |
|
Will push it forward in next few days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
It is just a poc to examine if the idea #11680 (comment) is promising.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?