Reuse ObjectMapper instances - #931
Merged
Merged
Conversation
Parsers previously created new `ObjectMapper` instances for every new parser instance. `BomParserFactory#createParser` (the main entrypoint for parsing) creates new parser instances on each invocation. Library consumers that parse many BOMs at high volume kept paying the price for Jackson re-initializing its `ObjectMapper`. Because it wasn't reused, its internal caching strategies for reflective lookups etc. could never take effect. Jackson specifically recommends reusing `ObjectMapper`s: https://github.com/fasterxml/jackson-docs/wiki/presentation:-jackson-performance#basics-things-you-should-do-anyway Signed-off-by: nscuro <nscuro@protonmail.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
🟢 Coverage 62.50% diff coverage · -0.01% coverage variation
Metric Results Coverage variation ✅ -0.01% coverage variation Diff coverage ✅ 62.50% diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (fa30309) 7833 5863 74.85% Head commit (39cdee5) 7831 (-2) 5861 (-2) 74.84% (-0.01%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#931) 16 10 62.50% Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
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
1 participant
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.
Parsers previously created new
ObjectMapperinstances for every new parser instance.BomParserFactory#createParser(the main entrypoint for parsing) creates new parser instances on each invocation.Library consumers that parse many BOMs at high volume kept paying the price for Jackson re-initializing its
ObjectMapper. Because it wasn't reused, its internal caching strategies for reflective lookups etc. could never take effect.Jackson specifically recommends reusing
ObjectMappers: https://github.com/fasterxml/jackson-docs/wiki/presentation:-jackson-performance#basics-things-you-should-do-anyway