Skip to content

Commit c28486e

Browse files
committed
docs: fix typo
1 parent 3d4908a commit c28486e

2 files changed

Lines changed: 6 additions & 8 deletions

File tree

crates/containerd-shim-wasmtime/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ upon receiving a terminate or interrupt signal in the container.
2727

2828
This can be very useful on the Wasm-first platforms to allow instance-per-request isolation:
2929

30-
> Eeach Wasm instance serves only one HTTP request, and then goes away. This is fantastic for security and bug
30+
> Each Wasm instance serves only one HTTP request, and then goes away. This is fantastic for security and bug
3131
> mitigation: the blast radius of an exploit or guest-runtime bug is only a single request, and can never see the data
3232
> from other users of the platform or even other requests by the same user. [3]
3333

docs/src/benchmarks.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -36,12 +36,10 @@ This is for Wasmtime shim. We use `hey` to load test the Wasmtime shim running "
3636

3737
We built a distroless container image with `wasmtime` runtime installed. Then we run stress-test for `wasmtime` shim and the distroless container for the same workload. The result is shown below.
3838

39-
| Runtime | Tasks | Time | Throughput |
40-
|---------|-------|------|------------|
41-
| runwasi wasmtime | 1000 | 3s 31ms 663us 672ns | 329.85 tasks/s |
42-
| runc distroless wasmtime | 1000 | 11s 795ms 27us 285ns | 84.78 tasks/s |
43-
44-
39+
| Runtime | Tasks | Time | Throughput |
40+
| ------------------------ | ----- | -------------------- | -------------- |
41+
| runwasi wasmtime | 1000 | 3s 31ms 663us 672ns | 329.85 tasks/s |
42+
| runc distroless wasmtime | 1000 | 11s 795ms 27us 285ns | 84.78 tasks/s |
4543

4644
The Dockerfile for the distroless container is shown below.
4745

@@ -85,6 +83,6 @@ We use [benchmark-action](https://github.com/benchmark-action/github-action-benc
8583

8684
If you want to contribute to the benchmarks, whether it's adding a new benchmark or improving the existing ones, or just want to share your ideas, please refer to the following issue:
8785

88-
- [Bencharking issue #97](https://github.com/containerd/runwasi/issues/97)
86+
- [Benchmarking issue #97](https://github.com/containerd/runwasi/issues/97)
8987

9088
Any PRs are welcome!

0 commit comments

Comments
 (0)