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
Let's not delete the cache on invalidation and just let it rot untill it's deleted by itself or flushed on deployment. Let's say we instead of deleting the keys in database on invalidation, set some value that would mean some TAG was invalidated at that given time.
On read, there would be always check (there could be lua script doing this saving bandwidth) that the key has tags and if it has tags, than there would be check when was the last time the tag was deleted and if the cache entry is older then the flushing by tag, no value would be returned but instead the one entry will be deleted.
Garbage collection could be done using maxmemory=volatile-ttl as stated in #20
someone must:
impelement proof-of-concept
test it on hight traffic site
The text was updated successfully, but these errors were encountered:
Inspiration: Cache – FileStorage without FileJournal with TAGS support – working solution
Let's not delete the cache on invalidation and just let it rot untill it's deleted by itself or flushed on deployment. Let's say we instead of deleting the keys in database on invalidation, set some value that would mean some TAG was invalidated at that given time.
On read, there would be always check (there could be lua script doing this saving bandwidth) that the key has tags and if it has tags, than there would be check when was the last time the tag was deleted and if the cache entry is older then the flushing by tag, no value would be returned but instead the one entry will be deleted.
Garbage collection could be done using
maxmemory=volatile-ttl
as stated in #20someone must:
The text was updated successfully, but these errors were encountered: