Major 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
- links to