[SERVER-56661] Evaluate increasing default close_handle_minimum in WiredTiger Created: 05/May/21  Updated: 21/Nov/23  Resolved: 19/Oct/21

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Josef Ahmad
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-56662 Evaluate increasing default close_han... Closed
Problem/Incident
Related
related to SERVER-24949 Lower WiredTiger idle handle timeout ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-10-04, Execution Team 2021-10-18, Execution Team 2021-11-01
Participants:
Linked BF Score: 3

 Description   

In SERVER-24949 we lowered the WiredTiger "close_idle_time" from 27 hours to 10 minutes. As a result, idle file handles may be closed more aggressively. This may have a performance impact for workloads that have long periods of idle activity, since closing idle handles also clears content from the cache.

Consider raising the "close_handle_minimum" threshold, which configures the number of file handles to keep open after a successful sweep, up from 250. This would prevent too many file handles from being closed during a sweep, and would be useful for workloads with a large number of collections and indexes. This may also raise the threshold for how long to keep around handles for dropped collections.



 Comments   
Comment by Githook User [ 19/Oct/21 ]

Author:

{'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}

Message: SERVER-56661 Increase close_handle_minimum from 250 to 2000
Branch: master
https://github.com/mongodb/mongo/commit/3ea8c504b8e7ecfab552858d610a239e00004b1e

Comment by Henrik Edin [ 23/Aug/21 ]

Spike for one sprint

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