3 ms·
That sounds very surprising... these numbers look pretty appalling for memcached... can anyone confirm that this is not simply due to a badly set-up memcached?
by swombat 18y ago
That sounds very surprising... these numbers look pretty appalling for memcached... can anyone confirm that this is not simply due to a badly set-up memcached? Or perhaps the author is not using memcached for its intended purpose?
I find it hard to believe that a widespread solution like memcached would be 100 times slower than one of its alternatives.
Also, all those numbers look awfully low.
- wheels 18y agoIt's pretty easy to see how much of the performance drop is protocol overhead since the numbers are there for Tokyo Cabinet / Tyrant over the memcached protocol and not. This isn't terribly surprising. One is a distributed network protocol, the other is just moving things around in memory. The poor performance for memcachedb doesn't surprise me a lot. In my tests I've found BDB (which it uses behind the scenes) to be frustratingly slow with writes.
- brendano 18y agothis is not the normal use case for memcached -- single client here.