[ 
https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198307#comment-15198307
 ] 

Remko Popma commented on LOG4J2-1318:
-------------------------------------

GC-free steady state logging is a big theme of the upcoming 2.6 release. You 
can track its progress in the LOG4J2-1270 epic and associated tickets. Feedback 
welcome!

However the LOG4J2-1270 work focusses on steady state logging, while it sounds 
like you experience issues during initialization. I don't know exactly what 
changes were made for LOG4J2-1180. Where are the temporary objects being 
created?


> LoggerContext#getLogger causes heavy GC overhead
> ------------------------------------------------
>
>                 Key: LOG4J2-1318
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1318
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.5
>            Reporter: Rodrigo Merino
>              Labels: performance
>
> 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:
> {code}
> -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
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to