[jboss-jira] [JBoss JIRA] (LOGMGR-263) Static Logger Lookup is much slower as with JDK 8
[
https://issues.jboss.org/browse/LOGMGR-263?page=com.atlassian.jira.plugin...
]
James Perkins commented on LOGMGR-263:
--------------------------------------
A static logger should have much better performance as the call stack would only be walked
when the logger is initialized. I had also thought that the Java 9+ {{StackWalker}} was
supposed to have better performance, but maybe not :).
Anyway so you're saying by removing the {{static}} keyword the performance is better?
Static Logger Lookup is much slower as with JDK 8
-------------------------------------------------
Key: LOGMGR-263
URL: https://issues.jboss.org/browse/LOGMGR-263
Project: JBoss Log Manager
Issue Type: Bug
Environment: WildFly 17, OpenJDK 11
Reporter: Andreas Liebscher
Priority: Major
Attachments: grafik1570016303722 (1).png, grafik1570016303722.png,
grafik1570016791285.png
During upgrading a Java EE application from WildFly 13 with JDK 8 to WildFly 17 with JDK
11 we had a serious performance issue. We identified the usage of the logging framework
SLF4J with the pattern `static Logger log =
LoggerFactory.getLogger(StatusChangeValidatorFactory.class)` was the reason when a lot of
calls to `getLogger` occur in parallel. As workaround we removed `static` from some code
hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8 got a
performance improvement with the removed `static` keyword.
Please check the VisualVM output as prove of JDKSpecific got slower:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)