We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://www.servicemesher.com/blog/202004-istio-envoy-wasm/
Istio 1.5 回归单体架构,并抛却原有的 out-of-process 的数据面(Envoy)扩展方式,转而拥抱基于 WASM 的 in-proxy 扩展,以期获得更好的性能。本文基于网易杭州研究院轻舟云原生团队的调研与探索,介绍 WASM 的社区发展与实践。
The text was updated successfully, but these errors were encountered:
清晰的文章! wasm纯cpu计算和native差别不大,但是一旦涉及到访存就麻烦了,因为wavm只能访问vm内的内存。这就和应用逻辑非常相关了。典型就是protobuf message操作导致读写放大。这些优化在持续进行
Sorry, something went wrong.
这个c++代码的PathRewriteRootContext中的rewrites_类型是什么呀?找了半天c++代码也没找到合适的
No branches or pull requests
https://www.servicemesher.com/blog/202004-istio-envoy-wasm/
Istio 1.5 回归单体架构,并抛却原有的 out-of-process 的数据面(Envoy)扩展方式,转而拥抱基于 WASM 的 in-proxy 扩展,以期获得更好的性能。本文基于网易杭州研究院轻舟云原生团队的调研与探索,介绍 WASM 的社区发展与实践。
The text was updated successfully, but these errors were encountered: