0
@@ -409,6 +409,102 @@ threads 32u Number of worker threads requested.
0
+CAVEAT: This section describes statistics which are subject to change in the
0
+The "stats" command with the argument of "items" returns information about
0
+item storage per slab class. The data is returned in the format:
0
+STAT items:<slabclass>:<stat> <value>\r\n
0
+The server terminates this list with the line
0
+The slabclass aligns with class ids used by the "stats slabs" command. Where
0
+"stats slabs" describes size and memory usage, "stats items" shows higher
0
+The following item values are defined as of writing.
0
+------------------------------
0
+number Number of items presently stored in this class. Expired
0
+ items are not automatically excluded.
0
+age Age of the oldest item in the LRU.
0
+evicted Number of times an item had to be evicted from the LRU
0
+outofmemory Number of times the underlying slab class was unable to
0
+ store a new item. This means you are running with -M or
0
+Note this will only display information about slabs which exist, so an empty
0
+cache will return an empty set.
0
+CAVEAT: This section describes statistics which are subject to change in the
0
+The "stats" command with the argument of "sizes" returns information about the
0
+general size and count of all items stored in the cache.
0
+WARNING: This command WILL lock up your cache! It iterates over *every item*
0
+and examines the size. While the operation is fast, if you have many items
0
+you could prevent memcached from serving requests for several seconds.
0
+The data is returned in the following format:
0
+The server terminates this list with the line
0
+'size' is an approximate size of the item, within 32 bytes.
0
+'count' is the amount of items that exist within that 32-byte range.
0
+This is essentially a display of all of your items if there was a slab class
0
+for every 32 bytes. You can use this to determine if adjusting the slab growth
0
+factor would save memory overhead. For example: generating more classes in the
0
+lower range could allow items to fit more snugly into their slab classes, if
0
+most of your items are less than 200 bytes in size.
0
+CAVEAT: This section describes statistics which are subject to change in the
0
+The "stats" command with the argument of "slabs" returns information about
0
+each of the slabs created by memcached during runtime. This includes per-slab
0
+information along with some totals. The data is returned in the format:
0
+STAT <slabclass>:<stat> <value>\r\n
0
+STAT <stat> <value>\r\n
0
+The server terminates this list with the line
0
+------------------------------
0
+chunk_size The amount of space each chunk uses. One item will use
0
+ one chunk of the appropriate size.
0
+chunks_per_page How many chunks exist within one page. A page by
0
+ default is one megabyte in size. Slabs are allocated per
0
+ page, then broken into chunks.
0
+total_pages Total number of pages allocated to the slab class.
0
+total_chunks Total number of chunks allocated to the slab class.
0
+used_chunks How many chunks have been allocated to items.
0
+free_chunks Chunks not yet allocated to items, or freed via delete.
0
+free_chunks_end Number of free chunks at the end of the last allocated
0
+active_slabs Total number of slab classes allocated.
0
+total_malloced Total amount of memory allocated to slab pages.
Comments
No one has commented yet.