-
Notifications
You must be signed in to change notification settings - Fork 470
compute,storage: reduce the size of cluster commands #32261
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
Merged
Merged
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
For reference, here are the memory layouts of the two enums before this change:
|
`ComputeCommand` and `StorageCommand` are enums, so their size is dependent on the size of the largest variant. Both contain some huge variants, in particular `UpdateConfiguration` and the ones describing dataflows to install, bringing the size of the enums to 3-4 KB. In contrast, the variant we send most frequently, `AllowCompaction`, is only 40 bytes in size, so when handling an `AllowCompaction` command, we waste 3-4 KB of space. Commands are stored in histories and channels, so this amount of waste can have an impact on our memory usage. This commit removes the waste and brings the size of the command enum down to 40 bytes by boxing large fields. This makes code creating commands a bit more noisy, but no way to avoid that I think.
antiguru
approved these changes
Apr 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
TFTR! |
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.
ComputeCommand
andStorageCommand
are enums, so their size is dependent on the size of the largest variant. Both contain some huge variants, in particularUpdateConfiguration
and the ones describing dataflows to install, bringing the size of the enums to 3-4 KB. In contrast, the variant we send most frequently,AllowCompaction
, is only 40 bytes in size, so when handling anAllowCompaction
command, we waste 3-4 KB of space. Commands are stored in histories and channels, so this amount of waste can have an impact on our memory usage.This PR removes the waste and brings the size of the command enum down to 40 bytes by boxing large fields. This makes code creating commands a bit more noisy, but no way to avoid that I think.
(First two commits are from #32258 and can be ignored here.)
Motivation
Tips for reviewer
I didn't try the reduce the size of the responses here for two reasons:
Frontiers
), so moving its data to the heap wouldn't safe much memory overall.That's not to say we shouldn't try to reduce the memory usage of responses too, just that it's less urgent.
Checklist
$T ⇔ Proto$T
mapping (possibly in a backwards-incompatible way), then it is tagged with aT-proto
label.