[SERVER-20797] Develop an algorithm to handle bursts of activity in connection pool Created: 07/Oct/15  Updated: 24/Jun/19  Resolved: 24/Jun/19

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

Type: Bug Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

NetworkInterfaceASIO's connection pool currently has uncapped size, and will grow as new concurrent requests come in. It would be nice to grow the pool instead based on some function that determined the optimal number of connections to spawn to control how many we make during bursts of activity. For example if we suddenly go from 0 pending requests to 1000, then back down again, we shouldn't really need to create 1000 connections, and we're probably stepping on our own feet by doing so.



 Comments   
Comment by Mira Carey [ 24/Jun/19 ]

This is gone away after the introduction of SERVER-29237 (the maxConnecting connectiong pool parameter) which provides a rate limiter to growth in the pool.

We don't directly address the description of this ticket, but believe that the problem it tried to solve is no longer present in the product

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