Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-1318

LoggerContext#getLogger causes heavy GC overhead

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.6
    • Component/s: Core
    • Labels:

      Description

      With the changes from LOG4J2-1180, when running performance testing scenarios, we are experiencing some throughput degradations due to an increase in the GC stall time.

      With the changes from LOG4J2-1180, the GC stall went from ~6% to ~11%, having an impact on the application of a reduction of ~32% of the operations throughput. The memory allocation rate both before and after the change is 4GB/s and 12GB/s respectively.

      In both cases, the relevant jvm configuration params were:

      -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintTenuringDistribution -XX:ErrorFile=%MHOME%/logs/err.log -Xloggc:%HOME%/logs/gc.log -XX:+HeapDumpOnOutOfMemoryError -XX:+AlwaysPreTouch -Xms2048m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+UseParNewGC -XX:NewSize=1024m -XX:+UseNUMA
      

        Attachments

          Activity

            People

            • Assignee:
              remkop@yahoo.com Remko Popma
              Reporter:
              elrodro83 Rodrigo Merino
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: