Skip to content

v1.0.1

Compare
Choose a tag to compare
@github-actions github-actions released this 29 Mar 01:12
· 837 commits to main since this release
e188b64

wazero v1.0.1 fixes a stdio glitch, improves performance and polishes documentation. We decided to cut an early patch mainly to ensure python works properly.

Python repl hang

Despite trying many things prior to v1.0.0, a glitch escaped us. @evacchi tried the VMware Labs python-wasm, and noticed a repl hang. Edo and @achille-roussel collaborated on a fix, which also ended up deleting tricky code. He verified python-wasm works, and @ncruces verified dcraw still works as well. Thank these folks for the teamwork and rigor!

Optimizations

Due to the nature of our team, you can expect optimizations in every release. A lot of work by @mathetake has been optimization both from line count and performance. There were only several days duration since v1.0.0, the culmination of work by Takeshi and @evacchi (with review support by @achille-roussel) resulted in less code and a slight bump in performance in an end user benchmark:

goos: darwin
goarch: arm64
pkg: github.com/dapr/components-contrib/bindings/wasm
           │   old.txt   │           new.txt            │
           │   sec/op    │   sec/op     vs base         │
Example-12   12.11µ ± 2%   12.02µ ± 1%  ~ (p=0.132 n=6)

pkg: github.com/dapr/components-contrib/middleware/http/wasm
                          │   old.txt   │              new.txt              │
                          │   sec/op    │   sec/op     vs base              │
Native/rewrite/rewrite-12   573.7n ± 0%   575.0n ± 0%       ~ (p=0.240 n=6)
Tinygo/rewrite/rewrite-12   1.161µ ± 1%   1.155µ ± 1%  -0.52% (p=0.026 n=6)
Wat/rewrite/rewrite-12      986.2n ± 0%   988.4n ± 1%       ~ (p=0.485 n=6)
geomean                     869.3n        869.0n       -0.03%

Docs

Our documentation improved in the last few days as well: @jcchavezs fixed some glitches on our home page around trying out wazero, @jerbob92 added PDFium tools to our users page, and @codefromthecrypt implemented @Xe's suggestion to improve our our walltime clock documentation. We really appreciate the pro-activity on user facing documentation!