[FEA] Global thread pool in benchmarks #16801
Labels
cuIO
cuIO issue
feature request
New feature or request
Performance
Performance related issue
tests
Unit testing for project
libcudf currently creates a new thread pool in each multi-threaded benchmark.
This makes reading multithreaded benchmarks very difficult, as the number of unique threads is huge.
Proposed solution:
Files with multithreaded benchmarks should declare a single global pool that's reused in all benchmarks.
The text was updated successfully, but these errors were encountered: