Lines Matching refs:requests

115 behavior of the command. If a flag requests a response flag (ie 't' for TTL
263   things.  Client should construct only valid requests.
341   requests.
381   requests.
416   requests.
588 pipelining of requests while saving bytes on the wire for responses. For
640 Further requests will see a 'Z' flag to indicate that another client has
754 will be marked as "stale", returning the X flag with mget requests.
1246 - "proxyreqs": Emits detailed timing logs about requests/responses being
1333 | proxy_conn_requests   | 64u     | Number of requests received by the proxy  |
1336 |                       |         | serving proxy requests                    |
1337 | proxy_req_active      | 64u     | Number of in-flight proxy requests        |
1338 | proxy_req_await       | 64u     | Number of in-flight proxy async requests  |
1366 | store_too_large       | 64u     | Number of rejected storage requests       |
1369 | store_no_memory       | 64u     | Number of rejected storage requests       |
1692 | get_hits        | Total number of get requests serviced by this class.     |
1693 | cmd_set         | Total number of set requests storing data in this class. |
1881 succeed; typically it is used for "get" requests where a missing or
1886 implementation, requests must be contained in a single UDP datagram, but
1887 responses may span several datagrams. (The only common requests that would
1888 span multiple datagrams are huge multi-key "get" requests and "set"
1889 requests, both of which are more suitable to TCP transport for reliability
1904 to differentiate between responses to outstanding requests if there are