1. 25 Mar, 2018 1 commit
    • antirez's avatar
      AOF: enable RDB-preamble rewriting by default. · 28d28ef3
      antirez authored
      There are too many advantages in doing this, RDB is faster to persist,
      more compact, much faster to load back. The main issues here are that
      the code is less tested because this was not the old default (so we are
      enabling it for the new 5.0 release), and that the AOF is no longer a
      trivially parsable format from now on. However the non-preamble mode
      will be supported in the future as well, if new data types will be
      added.
      28d28ef3
  2. 23 Mar, 2018 2 commits
  3. 22 Mar, 2018 12 commits
  4. 21 Mar, 2018 3 commits
  5. 20 Mar, 2018 6 commits
  6. 19 Mar, 2018 1 commit
  7. 16 Mar, 2018 6 commits
  8. 15 Mar, 2018 9 commits
    • antirez's avatar
      RDB: make RDB check aware of LFU/LRU opcodes. · b1aae86f
      antirez authored
      b1aae86f
    • antirez's avatar
      RDB: LRU/LFU branches missed continue. · 8176a2ee
      antirez authored
      8176a2ee
    • antirez's avatar
      RDB: Ability to load LFU/LRU info. · 1ce50a7a
      antirez authored
      1ce50a7a
    • antirez's avatar
      RDB: Ability to save LFU/LRU info. · d7a5c0eb
      antirez authored
      This is a big win for caching use cases, since on reloading Redis will
      still have some idea about what is worth to evict and what not.
      However this only solves part of the problem because the information is
      only partially propagated to slaves (on write operations). Reads will
      not affect slaves LFU and LRU counters, so after a failover the eviction
      decisions are kinda random until keys start to collect some aging/freq info.
      
      However since new slaves are initially populated via RDB file transfer,
      this means that if we spin up a new slave from a master, and perform an
      immediate manual failover (for instance in order to upgrade the master),
      the slave will have eviction informations to use for some time.
      
      The LFU/LRU info is persisted only if the maxmemory policy is set to one
      of the relevant type, even if no actual "maxmemory"  memory limit is
      set.
      d7a5c0eb
    • antirez's avatar
      CG: XINFO STREAM. · 66143616
      antirez authored
      66143616
    • antirez's avatar
      CG: XINFO GROUPS + output format changes. · d7d8cd0b
      antirez authored
      XINFO is mainly an observability command that will be used more by
      humans than computers, and even when used by computers it will be a very
      low traffic command. For this reason the format was changed in order to
      have field names. They'll consume some bandwidth and CPU cycles, but in
      this context this is much better than having to understand what the
      numbers in the output array are.
      d7d8cd0b
    • antirez's avatar
      CG: XINFO CONSUMERS implemented. · 0cf6b1e3
      antirez authored
      0cf6b1e3
    • antirez's avatar
      67eeeb0b
    • antirez's avatar
      8d8755c7