Lines Matching refs:time

13 than reopen them every time they need to store or retrieve data.  This
142 Some commands involve a client sending some kind of expiration time
145 Unix time (number of seconds since January 1, 1970, as a 32-bit
146 value), or a number of seconds starting from current time. In the
149 that, the server will consider it to be real Unix time value rather
150 than an offset from current time.
153 updated on second boundaries, which makes expiration time roughly +/- 1s.
243 - <exptime> is expiration time. If it's 0, the item never expires
245   items). If it's non-zero (either Unix time or offset in seconds from
246   current time), it is guaranteed that clients will not be able to
247   retrieve this item after the expiration time arrives (measured by
248   server time). If a negative value is given the item is immediately
402 The "touch" command is used to update the expiration time of an existing item
409 - <exptime> is expiration time. Works the same as with the update commands
410   (set/add/etc). This replaces the existing expiration time. If an existing
412   expiration time of "20", the item would then expire in 20 seconds.
429 expiration time of an existing items.
434 - <exptime> is expiration time.
485 exp   = expiration time
486 la    = time in seconds since last access
548 - l: return time since item was last accessed in seconds
579 - l: return time since item was last accessed in seconds
581 The above two flags return the value of "hit before?" and "last access time"
583 hit or always show an access time of "0" unless combined with the "u" flag.
615 access time.
667 system (CPU, database accesses, time, and so on).
859 TTL as well; limiting the amount of time an item will live while stale and
1032 - <2> is a highly aggressive mode which causes pages to be moved every time
1057   time. If switching from segmented to flat mode, the background thread will
1152   "key", "exp" (expiration time), "la", (last access time), "cas",
1193 time.
1229 - "fetchers": Currently emits logs every time an item is fetched internally.
1304 | time                  | 32u     | current UNIX time according to the server |
1308 | rusage_user           | 32u.32u | Accumulated user time for this process    |
1310 | rusage_system         | 32u.32u | Accumulated system time for this process  |
1363 |                       |         | with a new expiration time                |
1569                        time set had to be evicted from the LRU before it
1659 The feature can still be enabled at start time via `-o track_sizes` and has a
1736 |                     | the time since the start of the command, so if       |
1768 TLS is a compile-time opt-in feature available in versions 1.5.13 and later.
1788 |                                |          | elapsed since the last time    |
1806 items whose update time is earlier than the time at which flush_all
1812 same time (which could e.g. cause a spike in database load with all