[SERVER-3598] use a thread pool for client connections Created: 15/Aug/11  Updated: 03/Feb/16  Resolved: 21/Jan/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Dwight Merriman Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

it would be nice to use a thread pool for conn threads. in high connect rate situations this would help the OS learn the amount of stack being used per thread; otherwise the lifetime of each thread may be too short for any adaption to be possible.



 Comments   
Comment by Dwight Merriman [ 03/Feb/16 ]

i see the confusion this is a duplicate ticket rather than "works as designed"... Well, it does work as designed technically especially way back.

Comment by Dwight Merriman [ 03/Feb/16 ]

there are a number of thread pools in the server code, although what you want specifically I think is this ticket: https://jira.mongodb.org/browse/SERVER-929

Comment by YANG Chenghu [ 03/Feb/16 ]

Hi Eliot, MongoDB server had connection and thread pool, are you sure ?

i check the code, MyMessageHandler doesn't have any thread pool, every client connection accept, create one thread.

please check it

Comment by Eliot Horowitz (Inactive) [ 21/Jan/14 ]

We have various connection pools, in server and clients.

Generated at Thu Feb 08 03:03:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.