Use slab class growth factor for slab size limit

Re Colin:
"When using a growth factor smaller than 2.0, the normal growth stops once
the chunk size reach half the page size (1 MB by default)."

This adds two more slab classes by default, but makes memcached a little
more efficient for larger values. This will create a *lot* more slabs if
you are increasing the page limit via -I

However, if you're lowering the memory limit, this helps keep things
efficient.
-Dormando

1 files changed, 1 insertions, 1 deletions

diff --git a/slabs.c b/slabs.c
index 2974706..b769d52 100644
--- a/slabs.c
+++ b/slabs.c
@@ -116,7 +116,7 @@ void slabs_init(const size_t limit, const double factor, const bool prealloc) {
 
     memset(slabclass, 0, sizeof(slabclass));
 
-    while (++i < POWER_LARGEST && size <= settings.item_size_max / 2) {
+    while (++i < POWER_LARGEST && size <= settings.item_size_max / factor) {
         /* Make sure items are always n-byte aligned */
         if (size % CHUNK_ALIGN_BYTES)
             size += CHUNK_ALIGN_BYTES - (size % CHUNK_ALIGN_BYTES);