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
{{ message }}
This repository has been archived by the owner on Nov 2, 2021. It is now read-only.
Hi, I noticed that GETs do not result in writes to the disk. This makes sense for the common case.
I'm wondering if there are cases where fatcache would be required to write to disk in the future? e.g. support CAS, maintain state of cache across power cycle.
BTW, Is there a plan to support "persistent" fatcache that keeps state across power cycle? Is a persistent memcache useful in real deployments?
Thanks.
The text was updated successfully, but these errors were encountered:
"persistent fatcache" does make sense. However, it would be difficult to achieve throughputs and latency similar to in-memory memcache because every read/write would go to ssd. This would make it persistent fatcache is non-viable replacement for in-memory memcache.
Hi, I noticed that GETs do not result in writes to the disk. This makes sense for the common case.
I'm wondering if there are cases where fatcache would be required to write to disk in the future? e.g. support CAS, maintain state of cache across power cycle.
BTW, Is there a plan to support "persistent" fatcache that keeps state across power cycle? Is a persistent memcache useful in real deployments?
Thanks.
The text was updated successfully, but these errors were encountered: