-
Notifications
You must be signed in to change notification settings - Fork 397
2.4x improvement in Cluster aggregation performance #692
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
Open
jdmarshall
wants to merge
6
commits into
siimon:master
Choose a base branch
from
jdmarshall:clusterLabels
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
623ecd2 to
571f8e1
Compare
Contributor
Author
|
This should fix #628 A lot of the gain here is that |
Contributor
Author
|
Node 20 did not support Iterator.filter?? I'm surprised it's still in LTS. Working on it. |
This was referenced Jul 29, 2025
b3916cd to
c37ed35
Compare
Collaborator
|
@jdmarshall sorry, missed this. Mind resolving the conflict? Your new benchmark runner has also landed 🙂 |
This also fixes issue with prettier.
…sult." This reverts commit ab12221.
This reverts most of commit 9251668. Except for some of the tests.
This has to wrestle with the problem of lack of fore-knowledge of the canonical set of labels. We achieve this by assuming 6 labels to begin with, first filling in the empties as we discover new ones, and tnen expanding the columns by ⌈25%⌉ if they don't, and re-keying the entire table (by concatenating extra ||'s onto the end).. Before and after: ✓ cluster ➭ aggregate() is 6.088% faster. ✓ cluster ➭ aggregate() is 149.4% faster.
c37ed35 to
104275f
Compare
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.
Use a similar strategy to LabelMap for stats coalescing for cluster.js
This has to wrestle with the problem of lack of fore-knowledge of the
canonical set of labels. We achieve this by assuming 6 labels to
begin with, first filling in the empties as we discover new ones, and
tnen expanding the columns by ⌈25%⌉ if they don't, and re-keying the
entire table (by concatenating extra ||'s onto the end)..