Details
-
Improvement
-
Resolution: Won't Do
-
Major - P3
-
None
-
None
-
None
-
Service Arch
Description
Worker threads are currently able to start new worker threads and remove themselves from the active thread list. The causes behind these decisions are transparent only on the thread side. These control and analysis actions should mostly be on the controller side. If this happens, the majority of the atomic operations can be simplified/downgraded to single-thread alternatives and most of the locks can be removed. There is also the direct advantage of shifting work to the controller thread, which means the worker threads will generally be more efficient and system-friendly.