yutannihilation commented on PR #646:
URL: https://github.com/apache/sedona-db/pull/646#issuecomment-3937664418
Thanks for this!
Sorry for a noob question. Even if I include `sd.sql("SET
datafusion.runtime.metadata_cache_limit = '900M'").execute()`, the benchmark
still doesn't improve much. Is this expected at the moment (until the new
version of DataFusion...?)? Maybe the difference is that DuckDB somehow holds a
persistent cache among sessions while SedonaDB doesn't?
Benchmark results (seconds):
| Engine | Median | Mean | Min | Max | Runs | row_count | max_confidence |
|---|---:|---:|---:|---:|---:|---:|---:|
| DuckDB | 0.591740 | 2.654925 | 0.575550 | 6.797485 | 3 | 7471 |
0.999544084072 |
| SedonaDB | 9.257312 | 8.987796 | 8.034394 | 9.671681 | 3 | 7471 |
0.999544084072 |
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
