[
https://issues.apache.org/jira/browse/LOG4J2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160464#comment-17160464
]
ASF subversion and git services commented on LOG4J2-2898:
---------------------------------------------------------
Commit e50d94cb093d79974322b0f66e5db8248f3ee324 in logging-log4j2's branch
refs/heads/master from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=e50d94c ]
LOG4J2-2898 changelog
> Avoid initializing volatile fields to their default values
> ----------------------------------------------------------
>
> Key: LOG4J2-2898
> URL: https://issues.apache.org/jira/browse/LOG4J2-2898
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.13.3
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 2.14.0
>
>
> Contribution: [https://github.com/apache/logging-log4j2/pull/367]
> From Turbanov Andrey:
> {quote}It's known that writing to a {{volatile}} field has performance impact.
> It's true even if code initializes field with _default_ value.
> This PR cleans such redundant initialization and improves startup
> performance.
> See similar improvement in JDK codebase:
> [https://bugs.openjdk.java.net/browse/JDK-8145680].
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
