Comment #1 on issue 95 by trond.norbye: Memory allocation default change (-m < 40 doesn't work)
http://code.google.com/p/memcached/issues/detail?id=95

My thoughts:
* Always allocate all memory from the system up front. This makes it easier for the
end user to see how much memory the server will use...

* If you specify a really low memory limit (so that you cannot satisfy preallocation of a slab page to each slab class), disable the preallocation of memory into each slab class. Remember to write out a warning to the user that preallocation was
disabled, so that he might get OOM when storing objects.

* If you specify a really high maximum item limit, preallocation of memory into all of the different slab classes will eat up _a lot_ of memory (20G if you set -I100m), so I think we should disable preallocation of memory if it consumes more than lets say 20% of the total memory you gave memcached. (and we should of course warn the user)... Why? I believe that most of the objects stored in memcached will most likely
be relatively equal in size (with some exceptions).


--
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

Reply via email to