3 ms·
Memcached exists for two reasons: Popular languages that hit inflection points when in-memory caches exceeded a certain size, and network cards becoming lower l
by hinkley 4y ago
Memcached exists for two reasons: Popular languages that hit inflection points when in-memory caches exceeded a certain size, and network cards becoming lower latency than SATA hard drives.
The latter is a well known and documented phenomenon. The moment popular drives are consistently faster than network again, expect to see a bunch of people writing articles about using local or disk cache, recycling old arguments from two decades ago.
- staticassertion 4y agoOK but that's got nothing to do with the post.
- hinkley 4y agoOne, it’s covered in the article. Two, it has nothing to do with the post only if you ignore queuing theory. When you throttle requests for IO then the latency is proportional to the duration of all of the previous queries.
- twotwotwo 4y agoAgree with GP that this is getting pretty far off the article, but also--I think remote caches in datacenters are sometimes as much about making the cache shared as about the storage latency. If you have a lot of boxes running your application, sometimes it's nice to be able to do an expensive thing once per expiry period across the cluster, not once per expiry per app server. Or sometimes you want a cheap simple way to invalidate or write a new value for the full cluster. The throughput and latency of SSDs does make them a workable cache medium for some uses, with much lower cost/GB than RAM, but that can be independent of the local/remote choice.