[SERVER-77745] investigate nightly commit queue variance starting on 1/6 Created: 02/Jun/23  Updated: 16/Jun/23  Resolved: 05/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Daniel Moody Assignee: Daniel Moody
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

This work was generated from the monthly SDP metrics meeting.



 Comments   
Comment by Daniel Moody [ 05/Jun/23 ]

I verified this is related to cache hit/miss ratio. It appears the steadiness before is because we were getting 100% hit rates consistently, and then at some point we were unable to get 100% consistently, generally get some were between 95% and <100%, most likely due to increased prunning activity. In the case of per-variant caches this is expected as we prune a little bit a lot more.

However per variant caches were not introduced until feb 22. So that is not likely the original cause. I suspect earlier than that we were simply still prunning more as we were having size and management problems with the cache (which instigated the move to per-variant cache), and I assume size pressure was causing increased prunning activities.

Generated at Thu Feb 08 06:36:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.