SERVER_ERROR out of memory on small puts to memcache.

Matt Knox matthewknox at
Tue Oct 9 21:38:54 UTC 2007

cache-fu also prepends a namespace; in my case, that's "prodapp:".  That is
the 8 chars I refer to.  I should have said this-I'm not so much worried
about why python breaks at a larger length as I am that the error occurs at
all.  It seems to me that memcache should boot something out of cache and
store the small blob I submitted-I could understand the error if I was
attempting to store a large blob of data and the cache did not have a slab
big enough for it, but surely it can evict a larger object to store a small
one, no?

On 10/9/07, Eric Hodel <drbrain at> wrote:
> On Oct 9, 2007, at 11:59 , Matt Knox wrote:
> > I consistently get an out of memory error when performing  < 44
> > byte (key+data) puts to memcache, but when 'put'-ing the same key
> > with data that is long enough to exceed 44 chars key + data  , I
> > succeed.  I observe this behavior using both the ruby client
> > (memcache-client 1.5) and the python one (python-memcached),
> > although the python client seems to break at 59 chars, rather than 44.
> memcache-client's default mode of operation is to Marshal the values
> you're storing in memcached.  For a String this is 4 bytes of overhead.
> --
> Poor workers blame their tools. Good workers build better tools. The
> best workers get their tools to do the work for them. -- Syndicate Wars

(def (eval e l d c)
  (if  (atom? e)
      ((ahandler (type e)) e l d c)
      (eval (car e) l d
              (fun (x)
                 (evapp x (cdr e) l d c)))))
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the memcached mailing list