On 6/18/20 3:09 PM, Chris Hegarty wrote: >> On 18 Jun 2020, at 13:43, Aleksey Shipilev <sh...@redhat.com> wrote: >> Again, JDK-8247532 is the writing on the wall: we don't need 3rd party >> developers to tell if Record >> serialization works fast in 15 -- we already know it does not. > > I disagree. JDK-8247532 is under review and well on its way towards JDK 15 > (yes, during RDP 1). > My reading of Peter’s benchmark result is that Record deserialization *does > work fast*. What am > I missing. JDK-8247532 is the evidence that Records serialization performance story is not clear.
Even if we disregard that after JDK-8247532 [1] Records are still 8% slower, the _existence_ of JDK-8247532 indicates there are performance problems in the area. That evidence now needs to be compensated by much more evidence to the contrary. (Yes, I contracted a lot of Bayesian thinking from my statistician wife...) (Here were several paragraphs of further thoughts, but I realized it basically repeats what I said before.) -- Thanks, -Aleksey [1] https://mail.openjdk.java.net/pipermail/core-libs-dev/2020-June/067223.html RecordSerializationBench.deserializeClasses: 31.049 ± 0.235 us/op RecordSerializationBench.deserializeRecords: 33.588 ± 0.394 us/op
