[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213482#comment-15213482 ] Remko Popma commented on LOG4J2-1318: - Fixed in master: I've refactored the LoggerCon

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213472#comment-15213472 ] Remko Popma commented on LOG4J2-1318: - Looking further, SLF4JLoggerContext is impleme

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213443#comment-15213443 ] Remko Popma commented on LOG4J2-1318: - [~garydgregory], [~ralph.go...@dslextreme.com]

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198229#comment-15198229 ] Gary Gregory commented on LOG4J2-1318: -- What the measurement for? 2.5 vs. 2.4.1? Or

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199460#comment-15199460 ] Rodrigo Merino commented on LOG4J2-1318: The measurements were done fir 2.5 vs 2.

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ 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

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199491#comment-15199491 ] Mikael Ståldal commented on LOG4J2-1318: Can we use just the logger name as key i

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199465#comment-15199465 ] Rodrigo Merino commented on LOG4J2-1318: I think that avoiding the composite key

[jira] [Commented] (LOG4J2-1318) LoggerContext#getLogger causes heavy GC overhead

[ https://issues.apache.org/jira/browse/LOG4J2-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198474#comment-15198474 ] Remko Popma commented on LOG4J2-1318: - I see now: each call to LoggerContext.getLogge