kraken/koka_bench/cfold_table.md

| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|:---|---:|---:|---:|---:|
| `build/kraken/out/bench/kraken-cfold 5` | 24.5 ± 0.7 | 22.9 | 26.7 | 49.60 ± 32.45 |
| `build/java/out/bench/cfold 5` | 73.3 ± 7.0 | 59.0 | 84.9 | 148.58 ± 98.14 |
| `build/ocaml/ml-cfold 5` | 0.5 ± 0.3 | 0.2 | 2.2 | 1.00 |
| `build/swift/sw-cfold 5` | 2.2 ± 0.5 | 1.7 | 3.7 | 4.40 ± 3.04 |
| `build/cpp/cpp-cfold 5` | 0.9 ± 0.4 | 0.5 | 2.9 | 1.79 ± 1.46 |
| `build/haskell/hs-cfold 5` | 0.8 ± 0.4 | 0.5 | 2.6 | 1.53 ± 1.23 |
| `build/koka/out/bench/kk-cfold 5` | 0.5 ± 0.4 | 0.2 | 2.2 | 1.07 ± 1.06 |
Add cfold benchmark - can't go over 5 (though Koka uses 20) because wasm runs out of stack. Not entirely sure how to handle that - I imagine we're emitting far to much on the stack frame, but also I would hope wasmtime would optimize it, and I additionally can't find a way to raise wasmtime's limit from the cli... It is worth noting that Koka notes that cfold is a benchmark that can exhaust the stack 2022-05-17 23:34:46 -04:00			`\| Command \| Mean [ms] \| Min [ms] \| Max [ms] \| Relative \|`
			`\|:---\|---:\|---:\|---:\|---:\|`
Formatting fix, end to end test run 2022-05-19 00:56:18 -04:00			\| `build/kraken/out/bench/kraken-cfold 5` \| 24.5 ± 0.7 \| 22.9 \| 26.7 \| 49.60 ± 32.45 \|
			\| `build/java/out/bench/cfold 5` \| 73.3 ± 7.0 \| 59.0 \| 84.9 \| 148.58 ± 98.14 \|
			\| `build/ocaml/ml-cfold 5` \| 0.5 ± 0.3 \| 0.2 \| 2.2 \| 1.00 \|
			\| `build/swift/sw-cfold 5` \| 2.2 ± 0.5 \| 1.7 \| 3.7 \| 4.40 ± 3.04 \|
			\| `build/cpp/cpp-cfold 5` \| 0.9 ± 0.4 \| 0.5 \| 2.9 \| 1.79 ± 1.46 \|
			\| `build/haskell/hs-cfold 5` \| 0.8 ± 0.4 \| 0.5 \| 2.6 \| 1.53 ± 1.23 \|
			\| `build/koka/out/bench/kk-cfold 5` \| 0.5 ± 0.4 \| 0.2 \| 2.2 \| 1.07 ± 1.06 \|