Kontinuation commented on PR #24: URL: https://github.com/apache/sedona-db/pull/24#issuecomment-3277149127
> I wonder if this also happens if we run spatial join against DuckDB. I have investigated the performance characteristics using a profiler, both are using all available processors when running the spatial join benchmarks. But this could be a problem if we run benchmarks in a different environment, or using a different dataset. We should always understand the reasons behind those numbers produced by benchmarks > forcing a single thread is maybe unrealistic because in practice some of our per-batch and per-item overhead is amortized over multiple threads How does multithreading amortize per-batch and per-item overhead? Could you explain that a bit more? -- 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]
