Skip to content

[Due for payment 2025-05-13] [$250] [quality] Explore smarter handling of cache key eviction #59913

@mountiny

Description

@mountiny

Problem

To avoid local onyx data growing infinitely, we have implemented eviction logic to only allow a maximum of onyx keys in the db (maxCachedKeysCount). However, there seem to be bugs in the implementation of the eviction because we have found cases where the App gets into a weird state when the maximum is hit as for example here.

Solution

Develop a smarter key eviction strategy that will not influence the App functionality in a negative way while releasing resources that are not needed and keeping the App fast and responsive even for the largest accounts and heaviest users.

Issue OwnerCurrent Issue Owner: @muttmuure
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021915464098079907753
  • Upwork Job ID: 1915464098079907753
  • Last Price Increase: 2025-04-24

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type
No fields configured for issues without a type.

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions