Lines Matching refs:time

13 than reopen them every time they need to store or retrieve data.  This
82 Some commands involve a client sending some kind of expiration time
85 Unix time (number of seconds since January 1, 1970, as a 32-bit
86 value), or a number of seconds starting from current time. In the
89 that, the server will consider it to be real Unix time value rather
90 than an offset from current time.
163 - <exptime> is expiration time. If it's 0, the item never expires
165   items). If it's non-zero (either Unix time or offset in seconds from
166   current time), it is guaranteed that clients will not be able to
167   retrieve this item after the expiration time arrives (measured by
168   server time). If a negative value is given the item is immediately
322 The "touch" command is used to update the expiration time of an existing item
329 - <exptime> is expiration time. Works the same as with the update commands
330   (set/add/etc). This replaces the existing expiration time. If an existing
332   expiration time of "20", the item would then expire in 20 seconds.
403 - <2> is a highly aggressive mode which causes pages to be moved every time
476 time.
502 - "fetchers": Currently emits logs every time an item is fetched internally.
559 | time                  | 32u     | current UNIX time according to the server |
563 | rusage_user           | 32u.32u | Accumulated user time for this process    |
565 | rusage_system         | 32u.32u | Accumulated system time for this process  |
603 |                       |         | a new expiration time                     |
770                        time set had to be evicted from the LRU before it
934 |                     | the time since the start of the command, so if       |
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