I can replace wasmi by Cranelift, and boom, profit.
But… there is other ways to get even faster code execution — at the cost of a longer code compilation though.
For instance, LLVM can provide a very fast code execution, almost at native speed.
Or we can generate assembly code dynamically.
Well, there is multiple ways to achieve that.
What if a project could provide a WebAssembly virtual machine with multiple backends?Enter WasmerAnd it was at that specific time that I’ve been hired by Wasmer.
To be totally honest, I was looking at Wasmer a few weeks before.
It was a surprise and a great opportunity for me.
Well, the universe really wants this rewrite from wasmi to Wasmer, right ?????Wasmer is organized as a set of Rust libraries (called crates).
There is even a wasmer-runtime-c-api crate which is a C and a C++ API on top of the wasmer-runtime crate and the wasmer-runtime-core crate, i.
e.
it allows running the WebAssembly virtual machine as you want, with the backend of your choice: Cranelift, LLVM, or Dynasm (at the time of writing).
That’s perfect, it removes my Rust library between the PHP extension and wasmi.
Then php-ext-wasm is reduced to a PHP extension without any Rust code, everything goes to wasmer-runtime-c-api.
That’s sad to remove Rust from this project, but it relies on more Rust code!Counting the time to make some patches on wasmer-runtime-c-api, I’ve been able to migrate php-ext-wasm to Wasmer in 5 days.
By default, php-ext-wasm uses Wasmer with the Cranelift backend, it does a great balance between compilation and execution time.
It is really good.
Let’s run the benchmark, with the addition of php+wasmer(cranelift):rust-baseline: 287ms,php: 19,761ms,php+wasmi: 67,622ms,php+wasmer(cranelift): 2,365ms ????.
Finally, the PHP extension provides a faster execution than PHP itself!.php+wasmer(cranelift) is 8.
6 times faster than php to be exact.
And it is 28.
6 times faster than php+wasmi.
Can we reach the native speed (represented by rust-baseline here)?.It’s very likely with LLVM.
That’s for another article.
I’m super happy with Cranelift for the moment.
(See our previous blog post to learn how we benchmark different backends in Wasmer, and other WebAssembly runtimes).
More OptimizationsWasmer provides more features, like module caching.
Those features are now included in the PHP extension.
When booting the nbody.
wasm file (19kb), it took 4.
2ms.
By booting, I mean: reading the WebAssembly binary from a file, parsing it, validating it, compiling it to executable code and a WebAssembly module structure.
PHP execution model is: starts, runs, dies.
Memory is freed for each request.
If one wants to use php-ext-wasm, you don’t really want to pay that “booting cost” every time.
Hopefully, wasmer-runtime-c-api now provides a module serialization API, which is integrated into the PHP extension itself.
It saves the “booting cost”, but it adds a “deserialization cost”.
That second cost is smaller, but still, we need to know it exists.
Hopefully again, Zend Engine has an API to get persistent in-memory data between PHP executions.
php-ext-wasm supports that API to get persistent modules, et voilà.
Now it takes 4.
2ms for the first boot of nbody.
wasm and 0.
005ms for all the next boots.
It’s 840 times faster!ConclusionWasmer is a young — but mature — framework to build WebAssembly runtimes on top of.
The default backend is Cranelift, and it shows its promises: It brings a correct balance between compilation time and execution time.
wasmi has been a good companion to develop a Proof-Of-Concept.
This library has its place in other usages though, like very short-living WebAssembly binaries (I’m thinking of Ethereum contracts that compile to WebAssembly for instance, which is one of the actual use cases).
It’s important to understand that no runtime is better than another, it depends on the use case.
The next step is to stabilize php-ext-wasm to release a 1.
0.
0 version.
See you there!If you want to follow the development, take a look at @wasmerio and @mnt_io on Twitter.
wasmerio/php-ext-wasm????+????+????️ PHP extension to run WebAssembly binaries.
github.
com.. More details