[
https://issues.apache.org/jira/browse/LOG4J2-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652509#comment-16652509
]
ASF GitHub Bot commented on LOG4J2-2475:
----------------------------------------
Github user remkop commented on the issue:
https://github.com/apache/logging-log4j2/pull/218
I cannot imagine any program logging one million parameters so this
benchmark is perhaps a bit academic. :-)
In a realistic program a "large" parameter array is probably more like 100
elements (and I would not like to maintain a program that has a logging
statement with 100 parameters).
Can we measure again with an extreme case of 1000 parameters?
I suspect that with an array of 1000 (or even 10,000) elements we won't see
much difference between nulling out only the first 10 or the full array, in
which case it is more robust to simply null out the whole array.
> Limit reusable event.clear parameter clearing to argsCount
> ----------------------------------------------------------
>
> Key: LOG4J2-2475
> URL: https://issues.apache.org/jira/browse/LOG4J2-2475
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
>
> Larger parameter arrays may make their way into log4j when passed into the
> logger directly. These may take longer to clear, despite only containing one
> or two parameters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
