Here are some benchmark results from my json path ...
# multiplatform
e
Here are some benchmark results from my json path library across jvm, js, wasmJs, and linuxNative. Non jvm platforms have some catching up to do (I think they struggle here more because of intense GCing due to the benchmarking), but it's much better than the results were last year!
m
I am wondering though why the linux native version is doing so terribly bad compared to the JVM version. What terrible code must the Kotlin compiler be generating there? It would be interesting to run the JVM class files through GraalVM/native image in order to be able to compare two native solutions from the same Kotlin code on the same machine which have just been generated by different compiler pipelines. (With the (free) enterprise version of GraalVM and proper optimisation settings I’d expect the native result to be equally fast as the JVM version.)
e
I looked into it a few months ago, and IIRC it was the GC. The benchmark runs a lot of iterations. I think I tried running it with fewer iterations and the numbers were better. I should try again and see if that's the case.