-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
startup time of runtime-wasmtime shim #704
Comments
Do you have the startup time comparison between the native and wasm containers? |
|
Just curious - were you using the latest released Wasmtime shim, or using the shim built from the main branch? The latest released wasmtime shim had a bug that slows down the startup time by 1 second, which was fixed in main. I shall publish a new version for the wasmtime shim. Let me know though because that will make a big difference in startup time. |
Yes, I built it from the main branch of runwasi, with something like : cargo build --release --target=x86_64-unknown-linux-gnu --target-dir=./target/ -p containerd-shim-wasmtime (this is from 26 September) |
Some updates: I am working on adding more benchmarks and traces to the core crate and the Wasmtime shim with a hope that we can gain more insights on the performance of the shim. |
@sangeeta1998 Could you tell how you get the execution time of the container execution, I'm curious, there may be the reason that the compilation time of the wasm file. |
The startup time of wasm containers (with --runtime=io.containerd.wasmtime.v1 --platform=wasm) for the same container (once in native rust, and once as wasm) although the size of wasm image are much smaller than the native ones, the startup time with the wasmtime shim is much slower.
The text was updated successfully, but these errors were encountered: