Lines Matching refs:which

36 data from a server, it must use the length of the data block (which it
45 is a text string which should uniquely identify the data for clients
59 that the client expects one line of response, which will indicate
64 request). The client sends a command line, which includes all the
113   of severe server errors, which make it impossible to continue
116   case in which the server closes a connection to a client.
127 First, the client sends a command line which looks like this:
150   "cas" is a check and set operation which means "store this data but
153 - <key> is the key under which the client asks to store the data
172   including the delimiting \r\n. <bytes> may be zero (in which case
193 the reply, which may be:
219 which is received as a text line followed by a data block. After all
296 - <value> is the amount by which the client wants to increase/decrease
384 The slabs automove command enables a background thread which decides on its
403 - <2> is a highly aggressive mode which causes pages to be moved every time
413 The LRU Crawler is an optional background thread which will walk from the tail
510   cache. Useful in seeing if items being evicted were actually used, and which
537 a number of lines which look like this:
600 | cas_badval            | 64u     | Number of CAS reqs for which a key was    |
677 CAVEAT: This section describes statistics which are subject to change in the
732 |                   |          | which the background thread reads from.      |
740 CAVEAT: This section describes statistics which are subject to change in the
769 evicted_nonzero        Number of times an item which had an explicit expire
783 expired_unfetched      Number of expired items reclaimed from the LRU which
785 evicted_unfetched      Number of valid items evicted from the LRU which were
797 Note this will only display information about slabs which exist, so an empty
803 CAVEAT: This section describes statistics which are subject to change in the
861 CAVEAT: This section describes statistics which are subject to change in the
978 items whose update time is earlier than the time at which flush_all
984 same time (which could e.g. cause a spike in database load with all
1037 requests, both of which are more suitable to TCP transport for reliability