Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
-
None
Description
Currently reads are batched and issued from a separate thread pool of reading threads. However in the case that there is not read queuing due to the max # of parallel requests, switching threads is unnecessary and adds additional context swithing overhead.
In a benchmark I observed 5% cpu spent on LockSupport.park which some googling indicates is due to context switching.
Attachments
Issue Links
- links to