Improve performance of VariableOrigin instances #3164
Merged
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.
what
std::unique_ptr
and store it in astd::list
inVariableValue
'sOrigins
.Origins
in astd::vector
and constructsVariableOrigin
elements in-place on insertion.VariableOrigin
instance, this performs only one.std::vector
's growth strategy may even prevent the heap-allocation on additional insertions.reserveOrigin
method to notify when multiple insertions will be made, so that a call tostd::vector::reserve
can be made to perform a single allocation (and copy of previous elements) if necessary, and then just initialize the new elements in-place.why
This change increases performance of the
benchmark
test by about 2.5%.Additionally, the refactored code simplifies code used to initialize
VariableOrigin
instances.misc
Included script to download OWASP Core Ruleset v4 for benchmark execution.
This is part of a series of PRs to improve performance of the library (1/n).