1. 22 May, 2014 1 commit
  2. 23 Apr, 2014 1 commit
  3. 15 Apr, 2014 1 commit
  4. 21 Mar, 2014 1 commit
  5. 20 Mar, 2014 1 commit
  6. 31 Jan, 2014 6 commits
  7. 19 Dec, 2013 3 commits
  8. 11 Dec, 2013 1 commit
  9. 06 Dec, 2013 1 commit
  10. 05 Dec, 2013 3 commits
  11. 09 Oct, 2013 1 commit
  12. 08 Jul, 2013 3 commits
  13. 30 May, 2013 2 commits
  14. 27 May, 2013 1 commit
  15. 15 May, 2013 1 commit
    • antirez's avatar
      Added a define for most configuration defaults. · 310dbba0
      antirez authored
      Also the logfile option was modified to always have an explicit value
      and to log to stdout when an empty string is used as log file.
      
      Previously there was special handling of the string "stdout" that set
      the logfile to NULL, this always required some special handling.
      310dbba0
  16. 24 Apr, 2013 1 commit
  17. 04 Apr, 2013 1 commit
  18. 06 Mar, 2013 1 commit
  19. 04 Mar, 2013 1 commit
  20. 12 Feb, 2013 1 commit
  21. 09 Feb, 2013 1 commit
  22. 08 Feb, 2013 1 commit
  23. 05 Feb, 2013 1 commit
  24. 03 Feb, 2013 1 commit
  25. 28 Jan, 2013 2 commits
  26. 19 Jan, 2013 1 commit
  27. 14 Dec, 2012 1 commit
    • antirez's avatar
      serverCron() frequency is now a runtime parameter (was REDIS_HZ). · f1481d4a
      antirez authored
      REDIS_HZ is the frequency our serverCron() function is called with.
      A more frequent call to this function results into less latency when the
      server is trying to handle very expansive background operations like
      mass expires of a lot of keys at the same time.
      
      Redis 2.4 used to have an HZ of 10. This was good enough with almost
      every setup, but the incremental key expiration algorithm was working a
      bit better under *extreme* pressure when HZ was set to 100 for Redis
      2.6.
      
      However for most users a latency spike of 30 milliseconds when million
      of keys are expiring at the same time is acceptable, on the other hand a
      default HZ of 100 in Redis 2.6 was causing idle instances to use some
      CPU time compared to Redis 2.4. The CPU usage was in the order of 0.3%
      for an idle instance, however this is a shame as more energy is consumed
      by the server, if not important resources.
      
      This commit introduces HZ as a runtime parameter, that can be queried by
      INFO or CONFIG GET, and can be modified with CONFIG SET. At the same
      time the default frequency is set back to 10.
      
      In this way we default to a sane value of 10, but allows users to
      easily switch to values up to 500 for near real-time applications if
      needed and if they are willing to pay this small CPU usage penalty.
      f1481d4a