summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHarel Ben-Attia <harelba@gmail.com>2019-11-05 14:17:39 +0200
committerGitHub <noreply@github.com>2019-11-05 14:17:39 +0200
commit169a9436a5dfa2eb6023b02db3caf2c5c0cfc5b2 (patch)
tree4798e33f640f2c8881cf28184b49505baff39b64
parent85fecec4de716a8e0dc5e513267da98c44d7f20c (diff)
Update BENCHMARK.md
-rw-r--r--test/BENCHMARK.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/test/BENCHMARK.md b/test/BENCHMARK.md
index 0337437..80146b2 100644
--- a/test/BENCHMARK.md
+++ b/test/BENCHMARK.md
@@ -14,7 +14,7 @@ This is an initial version of the benchmark, along with some results. The follow
The q version used for the benchmark is still on the python2/3 compatibility branch (hash f0b62b15b91583cd944ea2e8daf6f730198959fa)
-This is by no means a scientific benchmark, and it only focuses on the data loading time. Also, it does not try to provide any usability comparison between q and textql. Actually, I've created this benchmark in order to compare q over python 2 and 3, and only then decided it would be nice to add a similar comparison to textql.
+This is by no means a scientific benchmark, and it only focuses on the data loading time. Also, it does not try to provide any usability comparison between q and textql. Actually, I've created this benchmark in order to compare q over python 2 and 3, and only then decided it would be interesting to compare the results to textql and octosql.
## Methodology
The idea was to compare the time sensitivity of row and column count.
@@ -25,6 +25,8 @@ The idea was to compare the time sensitivity of row and column count.
The benchmark executes simple `select count(*) from <file>` queries for each combination, calculating the mean and stddev of each set of iterations. The stddev is used in order to measure the validity of the results.
+The graphs below only compare the means of the results, the standard deviations are written into the google sheet itself, and can be viewed there if needed.
+
## Hardware
OSX Sierra on a 15" Macbook Pro from Mid 2015, with 16GB of RAM, and an internal Flash Drive of 256GB.
@@ -67,7 +69,7 @@ The results from each of the benchmarks will be written to `<virtual-env-name>.b
## Updating the benchmark markdown document file
The results should reside in the following [google sheet](https://docs.google.com/spreadsheets/d/1Ljr8YIJwUQ5F4wr6ATga5Aajpu1CvQp1pe52KGrLkbY/edit?usp=sharing).
-* Duplicat the baseline tab inside the spreadsheet.
+* Duplicate the baseline tab inside the spreadsheet.
* Paste the content of `all.benchmark-results` to the new tab, near "Fill raw results here".
* All the graphs below will be updated automatically.