Memcached 1.5.16 release, high performance distributed caching system

memcached

Memcached is a high performance multithreaded event-based key/value cache store intended to be used in a distributed system.

memcached allows you to take memory from parts of your system where you have more than you need and make it accessible to areas where you have less than you need.

memcached also allows you to make better use of your memory. If you consider the diagram to the right, you can see two deployment scenarios:

  1. Each node is completely independent (top).
  2. Each node can make use of memory from other nodes (bottom).

The first scenario illustrates the classic deployment strategy, however you’ll find that it’s both wasteful in the sense that the total cache size is a fraction of the actual capacity of your web farm, but also in the amount of effort required to keep the cache consistent across all of those nodes.

With memcached, you can see that all of the servers are looking into the same virtual pool of memory. This means that a given item is always stored and always retrieved from the same location in your entire web cluster.

Also, as the demand for your application grows to the point where you need to have more servers, it generally also grows in terms of the data that must be regularly accessed. A deployment strategy where these two aspects of your system scale together just makes sense.

The illustration to the right only shows two web servers for simplicity, but the property remains the same as the number increases. If you had fifty web servers, you’d still have a usable cache size of 64MB in the first example, but in the second, you’d have 3.2GB of usable cache.

Changelog v1.5.16

Overview

Fixes critical potential segfault/memory corruption bug in 1.5.15 when storing items with client flags of “0”. Bug only exists in 1.5.15, and the fix is the only change in this release.

Fixes

  • When nsuffix is 0 space for flags hasn’t been allocated so don’t memcpy them.

Download