Comment #2 on issue 95 by [email protected]: Memory allocation default
change (-m < 40 doesn't work)
http://code.google.com/p/memcached/issues/detail?id=95
Trond's first two points mostly reiterate what I said.
I think on the third point... if a user has adjusted -I to be a high
number, and the
prealloc would take over a certain watermark of the memory limit, disable
prealloc...
I played with some numbers and I can see plenty of situations where people
can gum
themselve sup on it.
In the future the slab handler will be better about large items, I think.
In the
short term, the safest thing for us to do is disable the alloc reservation
(but
otherwise prealloc memory) if you've raised the -I default at all. Lowering
it should
not cause this. This should give the user a more deterministic behavior and
easier to
understand constraints.
So unless someone complaints in the next hour I'll implement just that :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
