-MEMCACHED_BEHAVIOR_SOCKET_RECV_SIZE
-
- Find the current size of SO_RCVBUF. A value of 0 means either an error
- occured or no hosts were available. It is safe to assume system default
- if this occurs. If an error occurs you can checked the last cached errno statement to find the specific error.
+Set this value to tune the number of messages that may be sent before libmemcached should start to automatically drain the input queue. Setting this value to high, may cause libmemcached to deadlock (trying to send data, but the send will block because the input buffer in the kernel is full).
+
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_IO_BYTES_WATERMARK
+
+Set this value to tune the number of bytes that may be sent before libmemcached should start to automatically drain the input queue (need at least 10 IO requests sent without reading the input buffer). Setting this value to high, may cause libmemcached to deadlock (trying to send data, but the send will block because the input buffer in the kernel is full).
+
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_IO_KEY_PREFETCH
+
+The binary protocol works a bit different than the textual protocol in that a multiget is implemented as a pipe of single get-operations which are sent to the server in a chunk. If you are using large multigets from your application, you may improve the latency of the gets by setting this value so you send out the first chunk of requests when you hit the specified limit. It allows the servers to start processing the requests to send the data back while the rest of the requests are created and sent to the server.
+
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_NOREPLY
+
+Set this value to specify that you really don't care about the result from your storage commands (set, add, replace, append, prepend).
+
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_NUMBER_OF_REPLICAS
+
+If you just want "a poor mans HA", you may specify the numbers of replicas libmemcached should store of each item (on different servers). This replication does not dedicate certain memcached servers to store the replicas in, but instead it will store the replicas together with all of the other objects (on the 'n' next servers specified in your server list).
+
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_RANDOMIZE_REPLICA_READ
+
+Allows randomizing the replica reads starting point. Normally the read is done from primary server and in case of miss the read is done from primary + 1, then primary + 2 all the way to 'n' replicas. If this option is set on the starting point of the replica reads is randomized between the servers. This allows distributing read load to multiple servers with the expense of more write traffic.
+
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_CORK
+
+This open has been deprecated with the behavior now built and used appropriately on selected platforms.
+
+
+.. c:type:: MEMCACHED_BEHAVIOR_KEEPALIVE
+
+Enable TCP_KEEPALIVE behavior.