Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-3153

FixedDateFormat performs poorly with a PreciseClock

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.14.1
    • 2.15.0
    • Layouts
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              ckozak Carter Kozak
              ckozak Carter Kozak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: