New Open Source Cache System
highscalability.com
highscalability.com
Likewise, storing to disk takes time rather than just storing in memory. Even if you store the objects in memory as well, writes are slower even though reads should be the same. A caching server shouldn't need its data to survive a crash since the authoritative copy should be in the database.
They're also quoting 20,000 transactions per minute depending on hardware. That doesn't seem that good. Considering that memcached handles 50,000 requests per second in its stock form or 200,000 requests per seocond with Facebook's modified version, 333 "transactions" per second doesn't sound so great. Maybe "transaction" is something other than a request for an object (maybe it's saving objects which sccache isn't optimized for).
It looks really cool, but before I would consider it I would want to know more about how it allocates memory and why they made some of the design decisions they made. I know that memcached put in its limitations in order to make it ultra fast and ultra scalable.