@@ -7,8 +7,8 @@ run on [current-bench](https://github.com/ocurrent/current-bench).
7
7
8
8
Benchmarking multicore algorithms tends to a require certain amount of setup,
9
9
such as spawning domains, synchronizing them before work, timing the work,
10
- collecting the times, and joining domains, that this framework tries to care of
11
- for you as conveniently as possible. Furthermore, benchmarking multicore
10
+ collecting the times, and joining domains, that this framework tries to take
11
+ care of for you as conveniently as possible. Furthermore, benchmarking multicore
12
12
algorithms in OCaml also involves a number of pitfalls related to how the OCaml
13
13
runtime works. For example, when only a single domain is running, several
14
14
operations provided by the OCaml runtime use specialized implementations that
@@ -34,7 +34,9 @@ benchmarks from the
34
34
[ Saturn] ( https://github.com/ocaml-multicore/saturn/tree/main/bench ) and
35
35
[ Kcas] ( https://github.com/ocaml-multicore/kcas/tree/main/bench ) libraries.
36
36
37
- We first open the [ ` Multicore_bench ` ] ( https://ocaml-multicore.github.io/multicore-bench/doc/multicore-bench/Multicore_bench/index.html ) module:
37
+ We first open the
38
+ [ ` Multicore_bench ` ] ( https://ocaml-multicore.github.io/multicore-bench/doc/multicore-bench/Multicore_bench/index.html )
39
+ module:
38
40
39
41
``` ocaml
40
42
# open Multicore_bench
@@ -158,7 +160,8 @@ val benchmarks : (string * Suite.t) list = [("Atomic", <fun>)]
158
160
```
159
161
160
162
Usually the list of benchmarks is in the main module of the benchmark executable
161
- along with an invocation of [ ` Cmd.run ` ] ( https://ocaml-multicore.github.io/multicore-bench/doc/multicore-bench/Multicore_bench/Cmd/index.html#val-run ) :
163
+ along with an invocation of
164
+ [ ` Cmd.run ` ] ( https://ocaml-multicore.github.io/multicore-bench/doc/multicore-bench/Multicore_bench/Cmd/index.html#val-run ) :
162
165
163
166
``` ocaml non-deterministic
164
167
# Cmd.run ~benchmarks ~argv:[||] ()
0 commit comments