[ https://issues.jboss.org/browse/LOGMGR-263?page=com.atlassian.jira.plugin... ] Andreas Liebscher updated LOGMGR-263: ------------------------------------- Description: 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 `Logger log = LoggerFactory.getLogger(XXX.class)` was the reason when a lot of calls to `getLogger` occur in parallel. As workaround we added `static` to some code hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8 got a performance improvement with the added `static` keyword. Please check the VisualVM output as prove of JDKSpecific got slower: was: 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: Summary: Logger Lookup is much slower as with JDK 8 (was: Static Logger Lookup is much slower as with JDK 8) -- This message was sent by Atlassian Jira (v7.13.8#713008)