duckdb / duckdb/duckdb-spatial
Question on Parallelism of spatial operations
Open
- Dominant language
- C
- Stars
- 708
- Forks
- 96
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 5
Description
I wanted to ask if duckdb spatial operations are in general single threaded or if they make use of parallelism with multiple threads as do most regular duckdb operations?
The documentation on spatial function states this for `ST_Read`
> Note that GDAL is single-threaded, so this table function will not be able to make full use of parallelism.
Is there guidance on which functions are/are not parallelisable? In my experience most spatial functions do make use of more threads.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.