4 ms·
Shakti themselves used rows as the comparison metric in the original link: https://shakti.com/database-software-history/ https://shakti.com/database-software-h
by anon1m0us 7y ago
Shakti themselves used rows as the comparison metric in the original link: https://shakti.com/database-software-history/ https://shakti.com/database-software-history/
Again, saying the speed of k is unrivaled is hype speak. You're adding negative value to the discussion.
- zerozerocool 7y agoTo give you an idea, here are some benchmarks comparing Python (with pandas/numpy) vs k (aka q/kdb+). https://www.linkedin.com/pulse/data-analysis-example-python-q-ferenc-bodon-ph-d-/ https://www.linkedin.com/pulse/data-analysis-example-python-... https://www.linkedin.com/pulse/lists-python-q-side-by-side-ferenc-bodon-ph-d-/ https://www.linkedin.com/pulse/lists-python-q-side-by-side-f... I think that software history page is meant to convey general workloads achievable, rather than performance. -(not the author of the benchmarks nor an employee of shakti FWIW)