4 ms·
Nearly completely nonsensical test. Aside from what was already written by others, this pretty much only tests function used to convert h3 geometry to h3 point.
by Hitton 4y ago
Nearly completely nonsensical test. Aside from what was already written by others, this pretty much only tests function used to convert h3 geometry to h3 point. It is provided in clickhouse out of the box, in other two you gotta get it from outside sources. The bigquery one is written in javascript - no wonder it's slow. Only useful fact is comparison of sizes of result tables between postgres and clickhouse.
- nl 4y agoUnless there is an alternative, benchmarking the software that you are going to use seems pretty reasonable.
- d4mi3n 4y agoI think OP was pointing out that this was an apple to oranges comparison—in that the comparison ends up being of little use due to poor rigor configuring each test case.
- marginalia_nu 4y agoThe thing is that it isn't informative. It only tells you that in this particular benchmark, such-and-such is so-much faster. This does not extrapolate to your real world use cases unless by some fluke it happens to be a major bottleneck in your application. The only actually informative benchmark is to port your application to use each of the the database engines, and then benchmark your application. That will maybe tell you something. Odds are what you were using before has a home field advantage by being fairly well optimized, so even then it doesn't tell you as much as you might believe.
- jhgb 4y agoAs I noted, you'd probably want to do this conversion before import anyway, so none of the results may be of practical interest if you decide to go down that road. But maybe query performance tests on already imported data would be of interest.