You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DateTimeUtils functions are somewhat inefficient when it comes to creation of objects. This is because the JDK does not allow creation of some instance types (e.g. ZonedDateTime) with primitives in the public interfaces. The result is a lot of unnecessary object create to convert, for example, nanos to seconds-with-nanos.
The current scaling makes some operations hit the heap max. Even though the operation completes, the benchmark results can be skewed because GC is spinning. This can result in a high operational variability between operation runs.
Re-scale the DateUtilsFormulaTest benchmarks to fit better in the available heap.
The text was updated successfully, but these errors were encountered:
The DateTimeUtils functions are somewhat inefficient when it comes to creation of objects. This is because the JDK does not allow creation of some instance types (e.g. ZonedDateTime) with primitives in the public interfaces. The result is a lot of unnecessary object create to convert, for example, nanos to seconds-with-nanos.
The current scaling makes some operations hit the heap max. Even though the operation completes, the benchmark results can be skewed because GC is spinning. This can result in a high operational variability between operation runs.
The text was updated successfully, but these errors were encountered: