For the record, #7986 is now fixed for jOOQ 3.12 and will be backported. I could achieve significant speedups when parsing OffsetDateTime manually, rather than through the OffsetDateTime.parse() method
On Friday, October 26, 2018 at 1:24:31 PM UTC+2, Lukas Eder wrote: > > The discussion has somehow gotten off-list. Back to the list now... > > On Thu, Oct 25, 2018 at 2:45 PM Lukas Eder <[email protected]> wrote: > >> >> but you’re right I’d much rather have #1 above. Also, just the >>> OffsetDateTime -> Instant improvement that came out of this thread will be >>> a nice win for *all* my queries when the next patch is released. :) >>> >> >> Yes, that's what I plan to work on these days >> > > I can reproduce this. In a trivial case where I run 10000 queries > producing 10000 timestamps each, a profiling session almost exclusively > runs through this parsing logic. I've created an issue to track this: > https://github.com/jOOQ/jOOQ/issues/7986 > > Further comments on the issue directly > > Thanks again for reporting, > Lukas > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
