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

fix: Reuse vector in LocalPartition #122

Closed
wants to merge 1 commit into from

Conversation

Yuhta
Copy link
Contributor

@Yuhta Yuhta commented Jan 2, 2025

Summary:
More than 10% of the CPU are spent on the destruction of local partition output when the load is high.

Also add some optimizations for serialization.

Differential Revision: D67742489

Summary:
More than 10% of the CPU are spent on the destruction of local partition output when the load is high.

Also add some optimizations for serialization.

Differential Revision: D67742489
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Meta Open Source bot. label Jan 2, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D67742489

Yuhta added a commit to Yuhta/velox that referenced this pull request Jan 2, 2025
Summary:
X-link: facebookincubator/nimble#122

More than 10% of the CPU are spent on the destruction of local partition output when the load is high.

Also add some optimizations for serialization.  Optimization on `ByteOutputStream::appendOneBool` does not show significant gain in the query in example (because they are a lot small batches), but it is net gain and would be significant in large batches, so I leave it in the code.

Differential Revision: D67742489
Yuhta added a commit to Yuhta/velox that referenced this pull request Jan 10, 2025
Summary:

X-link: facebookincubator/nimble#122

More than 10% of the CPU are spent on the destruction of local partition output when the load is high.

Also add some optimizations for serialization.  Optimization on `ByteOutputStream::appendBool` does not show significant gain in the query in example (because they are a lot small batches), but it is net gain and would be significant in large batches, so I leave it in the code.

Differential Revision: D67742489
Yuhta added a commit to Yuhta/velox that referenced this pull request Jan 10, 2025
Summary:

X-link: facebookincubator/nimble#122

More than 10% of the CPU are spent on the destruction of local partition output when the load is high.

Also add some optimizations for serialization.  Optimization on `ByteOutputStream::appendBool` does not show significant gain in the query in example (because they are a lot small batches), but it is net gain and would be significant in large batches, so I leave it in the code.

Differential Revision: D67742489
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in f858d12.

facebook-github-bot pushed a commit to facebookincubator/velox that referenced this pull request Jan 10, 2025
Summary:
Pull Request resolved: #12002

X-link: facebookincubator/nimble#122

More than 10% of the CPU are spent on the destruction of local partition output when the load is high.

Also add some optimizations for serialization.  Optimization on `ByteOutputStream::appendBool` does not show significant gain in the query in example (because they are a lot small batches), but it is net gain and would be significant in large batches, so I leave it in the code.

Reviewed By: xiaoxmeng

Differential Revision: D67742489

fbshipit-source-id: 8e70dd128f31caa7909ed7c1e2b4ac1e59d7c87d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Meta Open Source bot. fb-exported Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants