mecached - text protocol?

Anatoly Vorobey
Fri, 16 Jul 2004 22:29:28 +0300

On Fri, Jul 16, 2004 at 02:05:50PM -0500, Andy Bakun wrote:
> Is there a list of currently pending
> bottlenecks that will eventually be taken care of?  

We don't know of any. memcached was designed to, first and foremost, 
handle protocol requests as quickly as possible, and it never waits for 
anything but network in those code paths. Considering the fact that 
even a very, very busy memcached server has very low CPU usage 
percentage, it's safe to conclude that everything memcached does on 
its own in the critical code paths is completely dwarfed by 
network-related delays.

The one major change we're working on - moving to a different 
memory allocation model - would result in saving memory, not 
speeding memcached up. 

However, currently memcached's stability and speed come at a rather 
large price of memory waste. 

> Is "does too many
> string comparisons" on this list?

Of course not.

"There's nothing simply good, nor ill alone" -- John Donne