3 ms·

Thanks @cube2222! Great! Sorry for overlooking that option. I will definitely add that option to octosql to make the comparison fair. Should I add it to the 3 q

by dmoura 4y ago

Thanks @cube2222! Great! Sorry for overlooking that option. I will definitely add that option to octosql to make the comparison fair. Should I add it to the 3 queries?

cube2222 4y ago
No worries! I think it'll be most fair if I just let you know when these are fixed, and you can properly use them, performantly, with a sane output option (that's not stream native, but something like JSON). I.e. LIMIT won't work with stream_output. If you want to add it to the first one, I won't oppose, but don't feel pressured to do it. Especially the third query does highlight a very realistict limitation of OctoSQL as it works right now, so it's only fair as it is.
- cube2222 4y ago
  I've just released OctoSQL v0.6.0 which fixes the issue and adds eagerly printed CSV and JSON output, as well as a non-buffered LIMIT implementation. It's now just slightly slower in the benchmark than SPyQL. Thanks for the motivation!