Many Web 2.0 applications include a substantial amount of dynamic content. The pages of these applications generally cannot be generated once and then saved for reuse, and must be built from scratch in response to each request.
In order to make a Web 2.0 application run with an acceptable degree of efficiency, it is often necessary to do some application-level caching. The open source Memcached server is often used for this purpose. It is relatively easy to install Memcached on one or more servers, creating a single, cache which can expand to consume the available RAM on all of the servers if necessary. The cache can be checked before performing an expensive calculation or database lookup, often obviating the need for the calculation or the lookup. The results can be stored in the cache for the next time around. Properly implemented, a cache can provide a tremendous speed benefit while also reducing traffic to database and compute servers.
Gear6 has created a version of Memcached suitable for mission-critical work. This product is now available as an Amazon EC2 AMI.
Think of it as "Memcached as a service."
The Gear6 implementation of Memcached leverages the instance's local (ephemeral) storage,
providing a 100x cache capacity increase per instance (when compared to a purely RAM-based cache), while remaining 100% compatible with the existing memcached API. There's a web UI (shown at right) for monitoring, with access to 24 hours of historical usage and performance data.
The 32-bit (Small) instances are free (regular EC2 usage charges apply) and the 64-bit instances are available on an hourly basis, with prices ranging from $0.50 (Large) to $0.86 (Quad Extra Large) per hour, plus EC2 usage charges, including 24x7 support from Gear6. Get started now.
Memcached client libraries are available for every common programming language, including C / C++, PHP, Java, Python, Ruby, Perl, .Net, MySQL, PostgresQL, Erlang, Lua, LISP, and ColdFusion.
I'm really happy to see this offering from Gear6. As I note in this blog from time to time, powerful, high-level services like this allow application developers to spend more time focusing on the novel and value-added aspects of their application and less time on the underlying infrastructure.
-- Jeff;


Hi Jeff! This is Mark Atwood, Director of Community Development for Gear6. We're very excited about our new Web Cache for the Cloud product.
The page that people can go to to get started playing with and using it is
http://www.gear6.com/memcached-product/cloud-aws/
Posted by: mark.atwood.name | December 08, 2009 at 10:45 AM
BTW: Gear6 does all Memcached ops from memory (DRAM) as well. In fact, Gear6 increases DRAM efficiency because the G6 servers minimizes fragmentation and overly large bucket sizes for object storage.
In addition we leverage block based devices (disk for cloud, flash in data centre deployments) in conjunction with DRAM, essentially creating a two tiered cache. If the mix is appropriately balanced (which is what Gear6 Web Cache Server enforces) then the block storage device adds depth and is typically significantly faster than executing the application or db query (in the FIRST memcached operation that requires going to the block device). When the second op happens on that piece of data, it executes out of DRAM. Thus in aggregate the Gear6 server performs as if it were based 100% in DRAM but at significantly reduced cost. The trick is using the block storage appropriately (which is one of the things that the G6 Server optimizes).
If you do not want to leverage block storage, you do not have to and you can simply get the benefits of optimized DRAM utilization.
Posted by: joaquín.ruiz | December 11, 2009 at 04:39 PM