<https://twitter.com/bashorov/status/1674042199305...

# webassembly

[bashor]

https://twitter.com/bashorov/status/1674042199305011202

Special thanks to @Ilya Goncharov [JB]

[benkuly]

Awesome!

[Robert Jaros]

Doesn't work for me ...

[Robert Jaros]

Unhandled JavaScript exception: wasm validation error: at offset 123: bad type

[bashor]

Which browser do you use?

[Big Chungus]

Didn't work for me on Firefox Android either

[Big Chungus]

Same error

[rocketraman]

Try it on Chrome. @bashor I'm assuming play.kotlinlang.org is enrolled in the WasmGC origin trial?

[rocketraman]

If not, then chrome://flags/#enable-webassembly-garbage-collection

[Big Chungus]

Chrome Android works fine

[rocketraman]

So, totally unscientific crappy benchmark, BUT interesting as a starting point:

JVM: 173.841535 ms
JS: 98.2 ms
JS IR: 63.7 ms
WASM: 27.7 ms

Why is JVM so slow? Something to do with the way play runs this code on the JVM?

[rocketraman]

I guess JS, JS IR, and WASM are running on my local beefy box, JVM is running on some resource-constrained VM on the play server.

[Big Chungus]

I assume JVM hotspot doesn't have enough time to kick in

[rocketraman]

Yeah, but even putting the computeAck in a loop it gets a bit faster at 155 ms but doesn't improve beyond that. But like I said, crappy benchmark.

[Big Chungus]

Would be interesting to see a comparison on the same hardware

[Big Chungus]

Maybe even applying some "serverless" optimisations to jvm too

[rocketraman]

Yeah, with kotlinx-benchmark to set up a more reasonable microbenchmark environment

[Robert Jaros]

@bashor Firefox on Linux

[rocketraman]

@Robert Jaros Same issue here with Firefox on Linux, despite enabling wasm_function_references and wasm_gc.

[Robert Jaros]

The compose demo doesn't work as well (https://zal.im/wasm/creative/)

[Robert Jaros]

I'm almost sure it did work in the past ...

[Robert Jaros]

I'm using Firefox 114.0.2 at the moment

[rocketraman]

I note the Kotlin docs reference javascript.options.wasm_function_references and javascript.options.wasm_gc, but those aren't available options (any more?) in about:config. They can be added manually but don't exist by default.

[Big Chungus]

Ran kotlinx-benchmark on that ack fun. Here are the results (for comparison only)
• wasm: 62.658358974358976ms
• linuxX64: 243.702351ms
• js: 199.5830523333333ms
• jvm: 124.03912462037037ms

[Big Chungus]

JS IR on Nodejs
wasm on d8

[bashor]

Try it on Chrome. @bashor I’m assuming play.kotlinlang.org is enrolled in the WasmGC origin trial?

@rocketraman Sure 🙂

Didn’t work for me on Firefox Android either

@Big Chungus Try Firefox Nightly, but still you need to turn on flags at about:config, more here kotl.in/wasm_help

[bashor]

@Robert Jaros for Firefox GC proposals is available only in Nightly versions now, and not Origin Trials 😞 so you need to turn on features manually at about:config, more here kotl.in/wasm_help

[rocketraman]

https://kotlinlang.slack.com/archives/CDFP59223/p1687967537288999?thread_ts=1687957776.202199&amp;cid=CDFP59223
These are available on FF nightly, and it does work with these enabled. Shame the stable version doesn't even have these flags, even if disabled by default.

[bashor]

Don’t hesitate to vote https://bugzilla.mozilla.org/show_bug.cgi?id=1825077