4 ms·
Yes, that is correct. It began 2x slower than JS, and ended up 2x faster than JS.
by azakai 2y ago
Yes, that is correct. It began 2x slower than JS, and ended up 2x faster than JS.
- notRobot 2y agoI'm sorry I'm bad with translating numbers. This means originally the new version ran at half the speed of the JS version, but ended up running at double the speed? Pretty cool.
- azakai 2y agoYeah, exactly. The initial prototype turned out to be quite slow - a lot of optimizations are needed to be fast. The version as of now is 4x faster than that initial prototype, and 2x faster than the JS version. And we are working to make it even faster. The good news is that most of those optimizations weren't specific to Java, like work in V8 (that helps any Chromium-based-browser running WasmGC) and work in Binaryen (that helps any Binaryen-using toolchain, like Kotlin and Dart).
- azakai 2y ago(The post has since been updated to clarify that. Yeah, it was a little confusing before.)