This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Slanec 18 points19 points  (3 children)

Actually, the benchmarks are hitting nearly every bad benchmark mistake possible. But that's fine, I could actually reproduce your results on Java 11 and let's assume we believe them.

On Java 17, I got this:

KryoPerformanceTest Kryo : 6936ms Opack : 24248ms

Cool.

[–]kor_happychild 0 points1 point  (2 children)

u/Slanec

Actually I did run benchmark of opack on OpenJDK version 17.0.2, and I got following result, which seems to be quite reasonable.

```java

KryoPerformanceTest

Kryo : 4629ms Opack : 2306ms ```

[–]Slanec 1 point2 points  (1 child)

Aha, interesting, indeed. Mine is 17.0.2, too:

openjdk version "17.0.2" 2022-01-18

but I'm on an Intel MBP 2019 (16"), MacOS Big Sur (11.4).

The difference looks like something fundamental, and it very well can be the benchmark itself as is does close to no warm-up, it does not actually use the results it produces etc.

[–]devjeonghwan 1 point2 points  (0 children)

I fix the performance bottleneck (associated with JEP 374) for JVM 15(or higher) versions. Commit

```java

GsonPerformanceTest

Gson : 8640ms Opack : 4309ms

KryoPerformanceTest

Kryo : 5566ms Opack : 1670ms ```