tustvold opened a new issue, #6248: URL: https://github.com/apache/arrow-rs/issues/6248
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> Tokio is a cooperative threadpool and has strong assumptions that tasks yield frequently. Running CPU-bound work on the same threadpool results in poor throughput and can lead to connections getting dropped. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> We should add a with_runtime option to ParquetObjectReader that takes a tokio handle and spawns all work to the provided runtime. This encourages decoupling CPU-bound query execution / parquet decoding, from cooperatively scheduled IO. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> I'm aware of a number of codebases, such as InfluxDB IOx, that implement this spawning logic at the ObjectStore boundary instead. **Additional context** <!-- Add any other context or screenshots about the feature request here. --> https://github.com/apache/arrow-rs/pull/4040 attempted to add something similar to object_store, but concluded this really belongs in the integrations https://github.com/apache/arrow-rs/issues/5882 may be related to this -- 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]
