Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Cache Invalidation Behavior #566

Open
pozylon opened this issue Jun 15, 2023 · 0 comments
Open

Improve Cache Invalidation Behavior #566

pozylon opened this issue Jun 15, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@pozylon
Copy link
Member

pozylon commented Jun 15, 2023

Currently the Cache Invalidation can produce a high amount of intensive DB read queries. If there is 10'000's of products and extensive filter and custom filtering logic, the invalidation can take up a long time.

We should find ways to offload the invalidation of all mongodb caches to secondaryPreferred.

Also what I've been learning in the past few weeks:

  • Using the LRU-Cache system for localized text is a problem: Due to the way lru-cache works, when we have a big query it will not hit the cache, only on subsequent requests. memoizee works better as it can handle promises in a better way.
  • Using the dataloader is a real help, and we should find ways to use it more
@pozylon pozylon added the enhancement New feature or request label Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant