Skip to main content

Speed test of wasm at node vs deno vs wapm

Recently, I have created an app in Rust language for macOS then to make it cross-platform, ported it for other platforms using WebAssembly.

I have ported the app for these platforms:
  1. WAPM ⟶ Using WASI file as binary, i.e., generated via Rust
  2. Deno ⟶ Using WASM file as library, i.e., generated via Rust
  3. Node.js ⟶ Using WASM file as library, i.e., generated via Rust

Initially, I had made it on macOS where it runs very fast but on Windows it gets slowed down so much that is clearly visible.

So I tried to measure it somehow for which I took a command for the app which decodes the input parameter. Here is that command,

> ds -d 31kk ⟶ 3-1-2020

Now I need to measure the timelapse after each execution for which I'd used

> w32tm /query /status /verbose | find "Time since" && node ds -d 31kk && w32tm /query /status /verbose | find "Time since" && deno ds -d 31kk && w32tm /query /status /verbose | find "Time since" && wapm run ds -d 31kk && w32tm /query /status /verbose | find "Time since"

Where the application versions used for each platforms are
  • wapm ⟶ 0.4.1
  • node ⟶ 10.16.3
  • deno ⟶ 0.28.0

Observation

So I got the data, which after processing gave me below table after 5 iterations on each platform at Windows.

Iteration node deno wapm
1
3.265
3.410
5.651
2
3.347
3.792
5.573
3
3.381
3.517
5.575
4
3.190
3.529
5.688
5
3.412
3.577
5.672

In the above, table cell values are given in seconds.

Below is the plotted bar chart for this table.


Conclusion

As you can see in the chart the speed of node is highest while of wapm is lowest.

So the speed in order would be like this,


There is marginal difference in between node & deno which uses wasm in comparison to wapm which uses wasi.

The wapm is wasmer based package manager and wasi runtime.

Comments

Popular posts from this blog

Unlock protected blocks in Siemens SIMATIC Step 7

Recently I'd been called by Hindalco's Fabrication Plant division to unlock the protected blocks in Siemens SIMATIC Step 7. They were in need to unlock those blocks since an year because of 1 million Rupees of loss per month. They want to re-program those blocks but it was locked by the man who'd done the setup. From the people working in that department, I came to know that they were trying to call that man (someone from Italy) right here but he's not coming. Actually, what he'd done was that he'd locked some of the blocks and deleted the source file. And Siemens didn't provide any feature to unlock. Department people also told me that even the people working in Siemens don't know how to do it. Being a software engineer I know that any thing can be reverse engineered. So I took up the challenge. How did I unlocked the blocks? The first thing I'd done was searched about this software at Google and read about what is this software all about. Aft...

Launching a Jupyter Notebook with TensorFlow using Docker

This article will walk you through setting up a Jupyter Notebook environment with TensorFlow pre-installed using Docker. Docker allows you to run isolated containerized applications, providing a consistent environment regardless of your underlying operating system. Prerequisites: Docker: Ensure you have Docker installed and running on your system. You can download and install it from the official Docker website ( https://www.docker.com/ ). Steps: Start Docker: Open your Docker application (Docker Desktop for Windows/macOS or the command line if using Linux). Run the Jupyter Notebook container: For macOS/Linux: Open your terminal application and run the following command: docker run -it --rm -p 8888:8888 -v "${PWD}":/home/jovyan/work jupyter/tensorflow-notebook For Windows: Open your Command Prompt application and run the following command: docker run -it --rm -p 8888:8888 -v "%CD%":/home/jovyan/work jupyter/tensorflow-notebook Explanation of the command flags: -...

JS: The complete code example of Crypto.js (DES)

For one of the project I was trying to use crypto.js but I found that the Quick-start Guide have some deficiency in terms of library usage. So I am writing it here as a useful note for memory recap. <script src="http://crypto-js.googlecode.com/svn/tags/3.1.2/build/rollups/tripledes.js"></script> <script> var encrypted = CryptoJS.DES.encrypt("The secret message", "secret_key"); var e_msg = encrypted.toString(); console.log(e_msg); var decrypted = CryptoJS.DES.decrypt(e_msg, "secret_key"); var d_msg = decrypted.toString(CryptoJS.enc.Utf8); console.log(d_msg); </script>