Uploaded image for project: 'JBoss Log Manager'
  1. JBoss Log Manager
  2. LOGMGR-263

Logger Lookup is much slower as with JDK 8

    XMLWordPrintable

Details

    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:

      Attachments

        1. ClassInEar.java
          0.4 kB
        2. getlogger-stack.txt
          3 kB
        3. grafik1570016303722.png
          grafik1570016303722.png
          75 kB
        4. grafik1570016303722 (1).png
          grafik1570016303722 (1).png
          75 kB
        5. grafik1570016791285.png
          grafik1570016791285.png
          50 kB
        6. LogContextCacher.java
          2 kB
        7. logger-demo.war
          5 kB
        8. responsetimes.png
          responsetimes.png
          398 kB

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19267 [GSS](7.3.z) LOGMGR-263 - Logger Lookup is much slower as with JDK 8

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-19255 (7.2.z) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4806 Upgrade jboss-logmanager from 2.1.15.Final to 2.2.0.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4930 Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18947 [GSS](7.2.z) LOGMGR-263 - Logger Lookup is much slower as with JDK 8

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-4860 Performance degradation with the LogContextSelector on Java 11

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jperkins-rhn James Perkins
              mobilexagmuc Andreas Liebscher (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: