[
https://issues.apache.org/jira/browse/LOG4J2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283106#comment-17283106
]
Carter Kozak edited comment on LOG4J2-3017 at 2/11/21, 5:55 PM:
----------------------------------------------------------------
-I wonder if we could resolve this with CharSequence overloads to capture
GString and other similar types rather than pushing them through the Object
code path?
Alternatively our default message factories could check for instances of
CharSequence and use standard non-object messages in those cases, without
expanding the logger API.-
Disregard, commented before I read through the examples.
was (Author: ckozak):
I wonder if we could resolve this with CharSequence overloads to capture
GString and other similar types rather than pushing them through the Object
code path?
Alternatively our default message factories could check for instances of
CharSequence and use standard non-object messages in those cases, without
expanding the logger API.
> Groovy logging of GString with $ notation is very slow
> ------------------------------------------------------
>
> Key: LOG4J2-3017
> URL: https://issues.apache.org/jira/browse/LOG4J2-3017
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Liviu Carausu
> Assignee: Volkan Yazici
> Priority: Major
> Attachments: SomeClass.groovy, TestLogging.groovy
>
>
>
> Logging of GString is very slow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
