Using
memcached
1344
•
-n bytes
The minimum space allocated for the key+value+flags information. The default is 48 bytes.
•
-L
On systems that support large memory pages, enables large memory page use. Using large memory
pages enables
memcached
to allocate the item cache in one large chunk, which can improve the
performance by reducing the number misses when accessing memory.
•
-C
Disable the use of compare and swap (CAS) operations.
This option was added in
memcached
1.3.x.
•
-D char
Set the default character to be used as a delimiter between the key prefixes and IDs. This is used for
the per-prefix statistics reporting (see
Section 15.6.4, “Getting
memcached
Statistics”
). The default
is the colon (
:
). If this option is used, statistics collection is turned on automatically. If not used, you
can enable stats collection by sending the
stats detail on
command to the server.
This option was added in
memcached
1.3.x.
•
-R num
Sets the maximum number of requests per event process. The default is 20.
•
-B protocol
Set the binding protocol, that is, the default
memcached
protocol support for client connections.
Options are
ascii
,
binary
or
auto
. Automatic (
auto
) is the default.
This option was added in
memcached
1.4.0.
15.6.2.1.
memcached
Deployment
When using
memcached
you can use a number of different potential deployment strategies and
topologies. The exact strategy to use depends on your application and environment. When developing
a system for deploying
memcached
within your system, keep in mind the following points:
•
memcached
is only a caching mechanism. It shouldn't be used to store information that you cannot
otherwise afford to lose and then load from a different location.
• There is no security built into the
memcached
protocol. At a minimum, make sure that the servers
running
memcached
are only accessible from inside your network, and that the network ports being
used are blocked (using a firewall or similar). If the information on the
memcached
servers that is
being stored is any sensitive, then encrypt the information before storing it in
memcached
.
•
memcached
does not provide any sort of failover. Because there is no communication between
different
memcached
instances. If an instance fails, your application must capable of removing it from
the list, reloading the data and then writing data to another
memcached
instance.
• Latency between the clients and the
memcached
can be a problem if you are using different physical
machines for these tasks. If you find that the latency is a problem, move the
memcached
instances to
be on the clients.
• Key length is determined by the
memcached
server. The default maximum key size is 250 bytes.
• Try to use at least two
memcached
instances, especially for multiple clients, to avoid having a single
point of failure. Ideally, create as many
memcached
nodes as possible. When adding and removing
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...