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
One idea which me and @yurem discussed is to introduce 2 levels cache:
first level memory (bound to single node)
current cache implementation, provider with REDIS, MEMCACHED, NATIVE.
Get entry by key:
First check in-memory, if it's there return
If not in-memory, call second level cache (currently configured CacheProvider, e.g. NATIVE, REDIS, MEMCACHED).
Idea is on first level keep most used cache objects, and with memory speed is maximum, however that first level of cache is not going to be replicated. We should think whether it will not introduce problems in cluster.
The text was updated successfully, but these errors were encountered:
yuriyz
changed the title
Introduce second level memory cache for types of cache.
Introduce second level memory cache for all types of cache.
Sep 12, 2019
We can add TTL to each object type in first level cache
For example 30 seconds for attributes and scopes. This means that each node will evict these objects withing 30 seconds which is ok for this object type.
One idea which me and @yurem discussed is to introduce 2 levels cache:
Get entry by key:
Idea is on first level keep most used cache objects, and with memory speed is maximum, however that first level of cache is not going to be replicated. We should think whether it will not introduce problems in cluster.
The text was updated successfully, but these errors were encountered: