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

vam: Summarize use vector.Builder to materialize #5484

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

mattnibs
Copy link
Collaborator

The commit changes slow path aggregations to use vector.Builder when materializing the aggregation table. The previous approaching of creating a dynamic of consts was causing the system to run out of memory when querying larger datasets.

The commit changes slow path aggregations to use vector.Builder when
materializing the aggregation table. The previous approaching of
creating a dynamic of consts was causing the system to run out of memory
when querying larger datasets.
@mattnibs mattnibs requested a review from a team November 15, 2024 16:58
@philrz
Copy link
Contributor

philrz commented Nov 19, 2024

I just tested this branch out with the mgbench bench2/q5. Whereas previously it ended up consuming 110+ GB of RAM+swap on my Macbook and getting shot by the OOM killer it now reaches a max of ~4 GB of RAM usage and completes in mere seconds. So, a functional 👍 for me!

@mattnibs mattnibs merged commit 87ab6b7 into main Nov 20, 2024
3 checks passed
@mattnibs mattnibs deleted the summarize-materialize branch November 20, 2024 17:03
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.

3 participants