[SERVER-30738] Implement stdx::thread with control over stack sizes Created: 18/Aug/17  Updated: 08/Jan/24  Resolved: 24/Feb/22

Status: Closed
Project: Core Server
Component/s: Internal Code, Networking
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-69905 Improve ServiceExecutorSynchronous wo... Backlog
is related to SERVER-15902 use signal handling stack via sigalts... Closed
is related to SERVER-35542 Configurable service worker thread st... Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-08-26, Dev Tools 2019-09-09, Dev Tools 2019-09-23, Dev Tools 2019-10-07
Participants:

 Description   

We currently have two types of threads - 'normal' threads, created via std[x]::thread, and worker threads, created via launchServiceWorkerThread. The latter exists so that we can have explicit control over the worker thread stack size, which is not possible with a std::thread, or with our current implementation of stdx::thread, which is just a wrapper around std::thread.

We should implement our own stdx::thread which also allows for explicit control over stack sizes.



 Comments   
Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Comment by Andrew Morrow (Inactive) [ 13/Jun/18 ]

Note that this would also give us a mechanism to possibly implement SERVER-15902.

Generated at Thu Feb 08 04:24:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.