WWS workload with containerd shim taking more CPU as compared to other Wasm workloads #258
divya-mohan0209
started this conversation in
General
Replies: 3 comments 1 reply
-
Thank you for creating this discussion @divya-mohan0209! I think is worth taking a look at what is going on. Are you good if I upload the images here that were uploaded to Zulip? |
Beta Was this translation helpful? Give feedback.
0 replies
-
@ereslibre : I am sorry I just saw this now 😄 I uploaded the images & have provided more context in the next comment! wws workload when idle: ![]() spin workload when idle: ![]() |
Beta Was this translation helpful? Give feedback.
0 replies
-
Setup context:
If you'd like to replicate the setup, you can check out the demo repo. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is per the discussion on the Bytecode Alliance Zulip regarding Wasm workers server workloads taking way more memory (~38%) as compared to other Wasm workloads from the same example.
To do:
Provide more context about setupProvide screencaps from the BA Zulip here, as well.Beta Was this translation helpful? Give feedback.
All reactions