You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Carter Kozak (Jira)" <ji...@apache.org> on 2021/08/28 02:58:00 UTC

[jira] [Created] (LOG4J2-3153) FixedDateFormat performs poorly with a PreciseClock

Carter Kozak created LOG4J2-3153:
------------------------------------

             Summary: FixedDateFormat performs poorly with a PreciseClock
                 Key: LOG4J2-3153
                 URL: https://issues.apache.org/jira/browse/LOG4J2-3153
             Project: Log4j 2
          Issue Type: Bug
          Components: Layouts
    Affects Versions: 2.14.1
            Reporter: Carter Kozak
            Assignee: Carter Kozak


Enabling a PreciseClock with microsecond precision (default on jdk9+) results in substantially worse performance in DatePatternConverter using a FixedDateFormat which doesn't rely on microsecond precision.
The cached value is invalidated every time the microsecond clock changes. This is correct when the clock uses microsecond precision, however many configurations (including the default) use only millisecond precision, so we can reuse the cached value many times longer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)