Reserve vector capacity for tempTagMessages in TLog commit path #12571
+185
−0
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.
Pre-reserve capacity for the
tempTagMessagesvector incommitMessages()to eliminate dynamic reallocations during message parsing. ThetempTagMessagesvector grows dynamically as messages are parsed, causing multiple reallocations in the hot commit path. Each reallocation involves allocating new memory, copying existing elements, and freeing old memory. This happens on every TLog commit, adding unnecessary overhead.The PR estimates the number of messages based on total byte size and pre-reserve vector capacity:
A microbenchmark was written. Each tests simulate the commitMessages() parsing loop by creating realistic TagsAndMessage objects with variable sizes and pushing them into a vector. The benchmark measures three strategies: NoReserve (current implementation with dynamic growth), WithReserve (optimization using size estimation), and ExactReserve (theoretical "best case" with perfect knowledge of message count). Test scenarios cover typical TLog workloads from light (10 messages) to burst (5000 messages) loads.
Tests on playstation will be posted when completed.
Code-Reviewer Section
The general pull request guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.
For Release-Branches
If this PR is made against a release-branch, please also check the following:
release-branchormainif this is the youngest branch)