jiayuasu commented on PR #24: URL: https://github.com/apache/sedona-db/pull/24#issuecomment-3375166067
I think the main purpose of this benchmark is to serve as a unit test — to check whether our scalar function implementation introduces any unreasonable overhead. If we don’t make it default to a single thread, as DuckDB and PostGIS do for small datasets, then the results become largely meaningless. It doesn’t make sense to showcase SedonaDB’s performance using these numbers. For meaningful performance evaluation, we should instead use SpatialBench, which is designed exactly for that purpose. So let's merge it? -- 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]
