Skip to content

Commit 02c1990

Browse files
committed
Modify run instructions in README
1 parent 9e4a1b3 commit 02c1990

1 file changed

Lines changed: 1 addition & 7 deletions

File tree

README.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Typically a benchmark reports either the amount of work done over a constant amo
1111

1212
Benchmarks are often categorized based on their purpose and origin. Two such buckets are (1) codes written with the original intent of being user facing (hot paths in library codes, a typical application usage, etc) and (2) codes written specifically to target benchmarking some important or commonly used code construct or platform component. WasmScore does not aim to favor either of these benchmarking buckets as both are valuable in the evaluation of standalone Wasm performance depending on what you want to test and what you are trying to achieve.
1313

14-
## WasmScore principles
14+
## WasmScore Principles
1515
WasmScore aims to serve as a standalone Wasm benchmark and benchmarking framework that:
1616
- Is convenient to build and run with useful and easy to interpret results.
1717
- Is portable, enabling cross-platform comparisons.
@@ -44,16 +44,10 @@ Download and run the latest prebuilt benchmark image:
4444

4545
**X86-64:**
4646
```
47-
docker pull ghcr.io/bytecodealliance/wasm-score/wasmscore_x86_64_linux:latest
48-
```
49-
```
5047
docker run -it ghcr.io/bytecodealliance/wasm-score/wasmscore_x86_64_linux:latest
5148
```
5249
**AArch64:**
5350
```
54-
docker pull ghcr.io/bytecodealliance/wasm-score/wasmscore_aarch64_linux:latest
55-
```
56-
```
5751
docker run -it ghcr.io/bytecodealliance/wasm-score/wasmscore_aarch64_linux:latest
5852
```
5953

0 commit comments

Comments
 (0)