[SERVER-82707] Improve CatalogCache eviction policy Created: 02/Nov/23  Updated: 06/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Sulabh Mahajan
Resolution: Unresolved Votes: 0
Labels: car-product-sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
Assigned Teams:
Catalog and Routing
Sprint: CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
Participants:
Case:
Story Points: 3

 Description   

Currently the sharding catalog cache eviction policy is LRU with a hardcoded capacity of 10k entries. There are some improvements we could consider:

  • Making the capacity configurable.
  • Considering the size of the cached entry, which may vary wildly depending on each collection routing table size.
  • Being more aggressive in evicting long-unused entries.

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