You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2024. It is now read-only.
HI @anuraaga, thank you for releasing such a great GC strategy in proxy-wasm!
I am having trouble with the default GC in TinyGo(v0.27.0) as well.
When I try to compile my wasm plugin use nottinygc and follow the instructions in the readme, the compilation works. But when I deploy it into a k8s cluster with Istio(v1.14 and v1.16), the envoy shows the error when loading the wasm module.
Here is the error message inside envoy proxy.
Failed to load Wasm module due to a missing import: wasi_snapshot_preview1.sched_yield
Do you have any insights for such an issue? Appreciate your help!
The text was updated successfully, but these errors were encountered:
Thank you Anuraag for the quick response!
This works great now!
From my load testing result, the memory usage of Istio(that uses the default GC) increases linearly along with the traffic volume.
After replacing the gc and malloc with nottinygc, I didn't see too much CPU increment, but the memory usage will be stable at some level no matter how much the traffic volume is. This is brilliant!
HI @anuraaga, thank you for releasing such a great GC strategy in proxy-wasm!
I am having trouble with the default GC in TinyGo(v0.27.0) as well.
When I try to compile my wasm plugin use
nottinygc
and follow the instructions in the readme, the compilation works. But when I deploy it into a k8s cluster with Istio(v1.14 and v1.16), the envoy shows the error when loading the wasm module.Here is the error message inside envoy proxy.
Do you have any insights for such an issue? Appreciate your help!
The text was updated successfully, but these errors were encountered: