It might not be a specific bottleneck caused by some API method, but just generally that the JVM is extremely optimized and its runtime is very efficient, which isn’t quite the same with Native or other targets. The JVM has a slow start, but once it’s been running for a short while it becomes nearly as fast as native binaries.
Native code, generally, does typically run faster than JVM apps, but in this case Kotlin Native has its own runtime environment which is relatively new and isn’t nearly as highly optimized as the JVM. It’s not really expected to perform better than JVM apps at this time, though admittedly I don’t think it’s normally that much slower. 4-5x does seem quite excessive.
Short-lived objects could definitely be part of the issue, especially since it has a brand new GC. I recall in one of their blog posts about it that they’re focusing on correctness first, and will tackle GC performance later.
Also, you might want to try setting up some profiler tests in GitHub Actions on various OSs, to see if it’s related to the OS.