Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently, when submitting tasks to a thread pool, they are all commingled in a common queue. When a new task submitter shows up, they must wait in the back of the line behind all other queued tasks.
A simple alternative to this would be round-robin scheduling, where each new consumer is assigned a unique integer id, and the schedule / thread pool internally maintains the tasks associated with the consumer in separate queues.
Attachments
Issue Links
- is related to
-
ARROW-8667 [C++] Add multi-consumer Scheduler API to sit one layer above ThreadPool
- Open
-
ARROW-8765 [C++] Design Scheduler API
- Closed
-
ARROW-8767 [C++] Make ThreadPool task ordering configurable
- Open