NetWasm Narrows Gap With Mono AOT on Benchmarks

The project's 0.10 optimisation series, spanning releases 0.10.1 to 0.10.8, targets exception handling, bounds checks, SIMD and integer division.

Updated on Nov. 19, 2026 in Software

NetWasm Narrows Gap With Mono AOT on Benchmarks

NetWasm, a compiler and runtime that ahead-of-time compiles C# programs into standalone WebAssembly files, published a write-up of its 0.10 optimisation work covering releases 0.10.1 to 0.10.8. The project reports that NetWasm now outperforms Mono AOT on its own benchmark set.

Why it matters

The results show measurable speedups across exception handling, loops and numerical workloads for C# code targeting WebAssembly. They also illustrate how runtime design choices, such as the cost of register save-and-restore around functions that can throw, affect performance in WebAssembly environments.

The geometric mean of 0.41 across 2,213 cases means NetWasm at version 0.10.8 ran in roughly 41 percent of Mono AOT's time on average, with five cases excluded. The write-up does not report results on benchmarks outside the project's own set.

The players

NetWasm

NetWasm is a compiler and runtime project that compiles C# programs ahead of time into standalone WebAssembly files.

Mono AOT

Mono AOT is the ahead-of-time compilation mode of the Mono runtime for .NET-style code, used as the benchmark comparator in the NetWasm write-up.

The details

Throws in version 0.10.1 were routed through a shared function, cutting UI churn from 17.6 ms to 7.9 ms. Version 0.10.2 inlined small straight-line methods inside loops and skipped checks already performed on the same array and index, while SIMD support arrived in 0.10.7.

Timeline

  1. - 19 November 2026: Write-up of the NetWasm 0.10 optimisation work published.

Software Trajectory

NetWasm's results place it directly against Mono AOT, the established ahead-of-time option for C# code, and the write-up reports it now edges ahead on the project's benchmark set. This continues a pattern of compiling managed languages to WebAssembly to run outside the traditional .NET runtime.

Developers shipping C# code to WebAssembly may see faster execution for exception-heavy and numerical workloads, based on the project's reported benchmarks. The gains depend on the workload, so results on production code may differ from the project's own benchmark set.

The takeaway

Benchmark results from a single project's test suite are a useful signal but should be checked against your own workloads before changing toolchains. Measuring real code paths remains the most reliable way to judge whether a compilation approach helps.

Further reading

Explore more Software coverage for context on compilers and runtimes like NetWasm.

Source note: This article includes information reported by InfoQ.