Oracle 5.0 Reference Manual page 1363

Lock down all paged memory. This reserves the memory before use, instead of allocating new slabs
of memory as new items are stored in the cache.
Note
There is a user-level limit on how much memory you can lock. Trying to
allocate more than the available memory fails. You can set the limit for the
user you started the daemon with (not for the
by using
•
-v
Verbose mode. Prints errors and warnings while executing the main event loop.
•
-vv
Very verbose mode. In addition to information printed by -v, also prints each client command and
the response.
•
-vvv
Extremely verbose mode. In addition to information printed by -vv, also show the internal state
transitions.
•
-h
Print the help message and exit.
•
-i
Print the
memcached
•
-I mem
Specify the maximum size permitted for storing an object within the
supports a unit postfix
supported object size to 32MB:
shell> memcached -I 32m
The maximum object size you can specify is 128MB, the default remains at 1MB.
This option was added in 1.4.2.
•
-b
Set the backlog queue limit. The backlog queue configures how many network connections can be
waiting to be processed by memcached. Increasing this limit may reduce errors received by the client
that it is not able to connect to the
the server. The default is 1024.
•
-P pidfile
Save the process ID of the
•
-f
Set the chunk size growth factor. When allocating new memory chunks, the allocated size of new
chunks is determined by multiplying the default slab size by this factor.
To see the effects of this option without extensive testing, use the
the calculated slab sizes. For more information, see
Using
memcached
ulimit -S -l NUM_KB
and license.
libevent
(k for kilobytes, for megabytes). For example, to increase the maximum
m
memcached
instance into file.
memcached
1343
-u user
memcached
instance, but does not improve the performance of
-vv
Section 15.6.2.8, "memcached
user) within the shell
instance. The size
command-line option to show
Logs".