diff options
author | Harel Ben-Attia <harelba@gmail.com> | 2018-12-21 12:32:07 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-12-21 12:32:07 +0200 |
commit | 9ece4ad2c782bea6b339ab72f23d19198a5f2b6e (patch) | |
tree | 231a317796274c3ed379e12c42a12a129d0ac618 | |
parent | 394b4c8d97d41938d295c0d6a01e703c023dc680 (diff) |
Update BENCHMARK.md
-rw-r--r-- | test/BENCHMARK.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/BENCHMARK.md b/test/BENCHMARK.md index ddc7418..7b2a730 100644 --- a/test/BENCHMARK.md +++ b/test/BENCHMARK.md @@ -3,7 +3,7 @@ *Please don't use or publish this benchmark data yet, it's still alpha, i'm checking the validity of the results, and python 3 q version has not been merged yet.* **NOTE** -This just a preliminary benchmark, and the results I got are somewhat surprising. I would love to validate these results by having other people run the benchmark as well and send me emails with their results. If you're interested, please clone q, checkout the `q-benchmark` branch, and follow the "Running the benchmark" part, and send me the `all.benchmark-results` file, along with some details about your hardware. <harelba@gmail.com> +This just a preliminary benchmark, and the results I got are somewhat surprising. I would love to validate these results by having other people run the benchmark as well and send me emails with their results. If you're interested, please clone q, checkout the `q-benchmark` branch, and follow the "Running the benchmark" part. After the benchmark is finished, send me the `all.benchmark-results` file, along with some details about your hardware, and i'll add it to the spreadsheet. <harelba@gmail.com> # Benchmark This is an initial version of the benchmark, along with some results. The following is compared: |