[SERVER-58144] Consider an absolute dirty size to the eviction configuration parameters as default Created: 29/Jun/21  Updated: 28/Aug/23

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

Type: New Feature Priority: Major - P3
Reporter: Dmitry Agranat Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-38815 Expose an absolute dirty size to the ... Closed
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

Once SERVER-38815 is implemented, we can consider setting the new parameter as default



 Comments   
Comment by Louis Williams [ 02/Jul/21 ]

After we implement SERVER-38815 and we can observe the effects of tuning the eviction thresholds for users, we will revisit this ticket. Please comment with any data or relevant HELP tickets.

A high eviction threshold allows more dirty data to be kept in cache, which generally benefits read/write latencies for write-heavy workloads. If users are experiencing latency spikes due to checkpoints, we should also evaluate why checkpoints are so impactful and how to reduce their negative performance consequences.

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