kraken/koka_bench/cfold_table.md

| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|:---|---:|---:|---:|---:|
| `build/kraken/out/bench/kraken-cfold 5` | 26.0 ± 1.0 | 23.9 | 28.2 | 89.45 ± 114.65 |
| `build/kraken/out/bench/kraken-cfold-wavm 5` | 38.2 ± 0.8 | 36.8 | 40.7 | 131.51 ± 168.51 |
| `build/java/out/bench/cfold 5` | 69.4 ± 8.5 | 58.8 | 87.5 | 239.07 ± 307.69 |
| `build/ocaml/ml-cfold 5` | 0.4 ± 0.4 | 0.1 | 2.6 | 1.36 ± 2.23 |
| `build/swift/sw-cfold 5` | 1.8 ± 0.4 | 1.4 | 3.6 | 6.13 ± 7.99 |
| `build/cpp/cpp-cfold 5` | 0.7 ± 0.4 | 0.3 | 3.9 | 2.28 ± 3.27 |
| `build/haskell/hs-cfold 5` | 0.6 ± 0.3 | 0.3 | 3.7 | 1.93 ± 2.72 |
| `build/koka/out/bench/kk-cfold 5` | 0.3 ± 0.4 | 0.0 | 2.5 | 1.00 |
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 \|`
			`\|:---\|---:\|---:\|---:\|---:\|`
Benchmark adjustments and plotting 2022-07-06 21:26:10 -04:00			\| `build/kraken/out/bench/kraken-cfold 5` \| 26.0 ± 1.0 \| 23.9 \| 28.2 \| 89.45 ± 114.65 \|
			\| `build/kraken/out/bench/kraken-cfold-wavm 5` \| 38.2 ± 0.8 \| 36.8 \| 40.7 \| 131.51 ± 168.51 \|
			\| `build/java/out/bench/cfold 5` \| 69.4 ± 8.5 \| 58.8 \| 87.5 \| 239.07 ± 307.69 \|
			\| `build/ocaml/ml-cfold 5` \| 0.4 ± 0.4 \| 0.1 \| 2.6 \| 1.36 ± 2.23 \|
			\| `build/swift/sw-cfold 5` \| 1.8 ± 0.4 \| 1.4 \| 3.6 \| 6.13 ± 7.99 \|
			\| `build/cpp/cpp-cfold 5` \| 0.7 ± 0.4 \| 0.3 \| 3.9 \| 2.28 ± 3.27 \|
			\| `build/haskell/hs-cfold 5` \| 0.6 ± 0.3 \| 0.3 \| 3.7 \| 1.93 ± 2.72 \|
			\| `build/koka/out/bench/kk-cfold 5` \| 0.3 ± 0.4 \| 0.0 \| 2.5 \| 1.00 \|