810 High CPU in combination with openjdk11 and log4j2 #823
Conversation
This file contains 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
bgoorden
deleted the
bugfix/810-High-CPU-in-combination-with-openjdk11-and-log4j2
branch
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.
Issue link
All PRs MUST have a corresponding issue linked and issue number in PR name. i.e.:
Purpose
When using OpenJDK11 and log4j2 in combination with dozer mapper causes high cpu while stackwalking. Several issues have been reported in on the openjdk combination with log4j2.
Approach
Dozer creates loggers each time the map() function is called in 'MappingProcessor' and 'LogMsgFactory'. This causes stackwalking which drastically decreases performance.
While running a small test mapping objects, mapping times improved by 50%.
Open Questions and Pre-Merge TODOs