[SERVER-56662] Evaluate increasing default close_handle_minimum in WiredTiger Created: 05/May/21  Updated: 06/Dec/22  Resolved: 05/May/21

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-56661 Evaluate increasing default close_han... Closed
Assigned Teams:
Storage Execution
Participants:

 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 dictates when an idle handle sweep occurs, up from 250. This would prevent file handle sweeps from running as frequently, and only for workloads where the volume of idle handles is impactful, such as applications with many collections and indexes.



 Comments   
Comment by Louis Williams [ 05/May/21 ]

Closing due to Jira idempotency problems

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