You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: