A hybrid concurrent.futures executor is introduced to address the transition from I/O bound tasks to CPU-bound processing by implementing a multi-threaded approach across all available CPU cores. The executor aims to serve as a drop-in replacement for existing concurrent.futures executors while meeting both functional and non-functional expectations. User code should remain unchanged, utilizing existing executor functionalities to minimize code complexity and potential bugs. Simplification in coding structure, by potentially avoiding classes, is considered to enhance debuggability.
The organization of the code using subclasses and layers of delegation can complicate debugging, leading to the suggestion of simplifying the implementation by using functions instead.
The hybrid concurrent.futures executor aims to maximize CPU utilization by running multiple threads for I/O bound tasks while respecting required functional and non-functional needs.
Collection
[
|
...
]