[SERVER-34262] Move thread management to controller thread in ServiceExecutorAdaptive Created: 02/Apr/18 Updated: 06/Dec/22 Resolved: 02/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| 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. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ] |
|
The Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable. |