Sometimes, just adding a compiler flag can yield significant performance boosts. And that just happened. And that just happened. For about two years now, all major browsers have supported WASM (WebAssembly) SIMD. SIMD stands for “Single instruction, multiple data” and is a technology that permits CPUs to do some parallel computation, often speeding up the whole program. And that’s exactly why we tried it out recently. For about two years now WebAssembly “Single instruction, multiple data” We got positive results. The need for performance on the Web The Web platform is often overlooked as a viable target, because of its less-than-ideal environment and its perceived poor performance. And the perception is somewhat right: the Web environment has a lot of security-related quirks to take into account—the user needs to interact with a game frame before the browser allows it to play any sound1. Also, due to bandwidth and compatibility reasons, you rarely see high-fidelity games being played on a browser. Performance is better achieved when running software natively on the operating system. 1 But don’t underestimate the potential of the Web platform. As I explained in broad terms at the talk I gave at the last GodotCon Boston 2025, the Web has caught up a lot since the days of Flash games. Not only are there more people playing Web games every year, but standards and browsers improve every year in functionality and in performance. And that’s why we are interested in using WASM SIMD. WASM SIMD Benchmarks Our resident benchmark expert Hugo Locurcio (better known as Calinou) ran the numbers for us on a stress test I made. We wanted to compare standard builds to builds with WASM SIMD enabled. Calinou Note: You may try to replicate his results, but be aware that he has a beast of a machine. Here are his PC’s specifications: Note: CPU: Intel Core i9-13900K
GPU: NVIDIA GeForce RTX 4090
RAM: 64 GB (2×32 GB DDR5-5800 CL30)
SSD: Solidigm P44 Pro 2 TB
OS: Linux (Fedora 42) CPU: Intel Core i9-13900K CPU: GPU: NVIDIA GeForce RTX 4090 GPU: RAM: 64 GB (2×32 GB DDR5-5800 CL30) RAM: SSD: Solidigm P44 Pro 2 TB SSD: OS: Linux (Fedora 42) OS: I built a Jolt physics stress test from a scene initially made by passivestar. By spawning more and more barrels into the contraption, we can easily test the performance difference between the WASM SIMD build and the other. passivestar Without WASM SIMD

With WASM SIMD

Improvement (approx.)



Test links

Link

Link

-



Firefox 138(“+100 barrels” 3 times)

 

 

2×



Firefox 138(“+100 barrels” 6 times)

 

 

10.17×*



Chromium 134(“+100 barrels” 3 times)

 

 

1.37×



Chromium 134(“+100 barrels” 6 times)

 

 

14.17×* Without WASM SIMD

With WASM SIMD

Improvement (approx.)



Test links

Link

Link

-



Firefox 138(“+100 barrels” 3 times)

 

 

2×



Firefox 138(“+100 barrels” 6 times)

 

 

10.17×*



Chromium 134(“+100 barrels” 3 times)

 

 

1.37×



Chromium 134(“+100 barrels” 6 times)

 

 

14.17×* Without WASM SIMD

With WASM SIMD

Improvement (approx.) Without WASM SIMD Without WASM SIMD With WASM SIMD With WASM SIMD Improvement (approx.) Improvement (approx.) Test links

Link

Link

- Test links Test links Link Link Link Link Link Link - - Firefox 138(“+100 barrels” 3 times)

 

 

2× Firefox 138(“+100 barrels” 3 times) Firefox 138(“+100 barrels” 3 times) 2× 2× 2× Firefox 138(“+100 barrels” 6 times)

 

 

10.17×* Firefox 138(“+100 barrels” 6 times) Firefox 138(“+100 barrels” 6 times) 10.17×* 10.17×* 10.17× Chromium 134(“+100 barrels” 3 times)

 

 

1.37× Chromium 134(“+100 barrels” 3 times) Chromium 134(“+100 barrels” 3 times) 1.37× 1.37× 1.37× Chromium 134(“+100 barrels” 6 times)

 

 

14.17×* Chromium 134(“+100 barrels” 6 times) Chromium 134(“+100 barrels” 6 times) 14.17×* 14.17×* 14.17× *Please note that once the physics engine enters a “spiral of death”, it is common for the framerate to drop to single digits, SIMD or not. These tests don’t prove 10× to 15× CPU computing speed improvements, but rather that games will be more resilient to framerate drops on the same machine in the same circumstances. The 1.5× to 2× numbers are more representative here of the performance gains by WASM SIMD. *Please note that once the physics engine enters a “spiral of death”, it is common for the framerate to drop to single digits, SIMD or not. These tests don’t prove 10× to 15× CPU computing speed improvements, but rather that games will be more resilient to framerate drops on the same machine in the same circumstances. The 1.5× to 2× numbers are more representative here of the performance gains by WASM SIMD. What it means for your games Starting with 4.5 dev 5, you can expect your Web games to run a little bit more smoothly, without having to do anything. Especially when things get chaotic (for your CPU). It isn’t a silver bullet for poorly optimized games, but it will help nonetheless. Also, note that it cannot do anything for GPU rendering bottlenecks. Be aware that the stress tests are meant by nature to only test the worst case scenarios, so you may not see such large improvements in normal circumstances. But it’s nice to see such stark improvements when the worst happens. Availability From here on out, the 4.5 release official templates will only support WebAssembly SIMD-compatible browsers in order to keep the template sizes small. We generally aim to maintain compatibility with the oldest devices we can. But in this case, the performance gains are too large to ignore and the chances of users having browsers that are that far out of date is too small relative to the potential benefits. If you need to use non-SIMD templates, don’t fret. You can always build the Godot Editor and the engine templates without WebAssembly SIMD support by using the wasm_simd=no build option. build wasm_simd=no What’s next? As I wrote in my last blog post, we’re currently working very hard to make C#/.NET exports a reality. We do have a promising prototype, we just need to make sure that it’s production-ready. my last blog post a promising prototype I also mentioned in that article that I wanted to concentrate on improving our asset loading game. Preloading an entire game before even starting it hinders the ability to use Godot for commercial Web games. Once something is implemented to improve that issue, count on me to share the news with you. It’s either that, or we return to the old days of spam-webpages using the “Congratulations, you won!” sound effect when you least expect it. ↩ It’s either that, or we return to the old days of spam-webpages using the “Congratulations, you won!” sound effect when you least expect it. ↩ “Congratulations, you won!” ↩ Adam Scott Adam Scott Also published here Also published here here Photo by Haithem Ferdi on Unsplash Photo by Haithem Ferdi on Unsplash Haithem Ferdi Unsplash

NVIDIA

Intel

Godot's Web Performance Boost: Things to Know

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

A Look at Games Made With Godot XR (December 2024)

Create an IDE with Godot

Testing in Godot: How I Personally Approach It

The Noonification: Testing in Godot: How I Personally Approach It (3/7/2024)

Godot XR Update: The Top 5 Entries of the Godot XR Game Jam - March 2025

Godot 4.4.1 RC 2: What's New

A Look at Games Made With Godot XR (December 2024)

Create an IDE with Godot

Testing in Godot: How I Personally Approach It

The Noonification: Testing in Godot: How I Personally Approach It (3/7/2024)

Godot XR Update: The Top 5 Entries of the Godot XR Game Jam - March 2025

Godot 4.4.1 RC 2: What's New

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps