Conversation
When Feldera takes a profile, it measures the size of all the batches in each spine using SizeOf. This is very expensive for large batches, in some cases taking over a second of CPU time. This commit fixes the problem. Another way to fix the problem would be to calculate the exact size and save it. This could be done at batch creation time unconditionally, or the first time we measure it and cached. But this would still take the same large amount of CPU time, we'd just be able to avoid taking it more than once. And if we did it lazily and cached it, it would still take a lot of time in profiles, especially the first time a profile runs. Signed-off-by: Ben Pfaff <blp@feldera.com>
ryzhyk
approved these changes
Apr 6, 2026
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
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.
When Feldera takes a profile, it measures the size of all the batches in each spine using SizeOf. This is very expensive for large batches, in some cases taking over a second of CPU time. This commit fixes the problem.
Another way to fix the problem would be to calculate the exact size and save it. This could be done at batch creation time unconditionally, or the first time we measure it and cached. But this would still take the same large amount of CPU time, we'd just be able to avoid taking it more than once. And if we did it lazily and cached it, it would still take a lot of time in profiles, especially the first time a profile runs.
Describe Manual Test Plan
I am running the unit tests.