1. 27 Aug, 2014 1 commit
  2. 28 Jul, 2014 1 commit
  3. 25 Jul, 2014 1 commit
  4. 09 Jul, 2014 1 commit
  5. 21 Jun, 2014 1 commit
    • antirez's avatar
      Client types generalized. · b6a26b52
      antirez authored
      Because of output buffer limits Redis internals had this idea of type of
      clients: normal, pubsub, slave. It is possible to set different output
      buffer limits for the three kinds of clients.
      
      However all the macros and API were named after output buffer limit
      classes, while the idea of a client type is a generic one that can be
      reused.
      
      This commit does two things:
      
      1) Rename the API and defines with more general names.
      2) Change the class of clients executing the MONITOR command from "slave"
         to "normal".
      
      "2" is a good idea because you want to have very special settings for
      slaves, that are not a good idea for MONITOR clients that are instead
      normal clients even if they are conceptually slave-alike (since it is a
      push protocol).
      
      The backward-compatibility breakage resulting from "2" is considered to
      be minimal to care, since MONITOR is a debugging command, and because
      anyway this change is not going to break the format or the behavior, but
      just when a connection is closed on big output buffer issues.
      b6a26b52
  6. 22 Apr, 2014 1 commit
  7. 16 Apr, 2014 1 commit
  8. 31 Jan, 2014 3 commits
  9. 19 Dec, 2013 3 commits
  10. 12 Dec, 2013 1 commit
  11. 06 Dec, 2013 1 commit
  12. 05 Dec, 2013 3 commits
  13. 11 Jul, 2013 2 commits
  14. 08 Jul, 2013 1 commit
  15. 30 May, 2013 2 commits
  16. 27 May, 2013 1 commit
  17. 15 May, 2013 1 commit
    • antirez's avatar
      Added a define for most configuration defaults. · 180cfaae
      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.
      180cfaae
  18. 24 Apr, 2013 1 commit
  19. 06 Mar, 2013 1 commit
  20. 04 Mar, 2013 1 commit
  21. 12 Feb, 2013 1 commit
  22. 11 Feb, 2013 2 commits
  23. 05 Feb, 2013 1 commit
  24. 04 Feb, 2013 1 commit
  25. 28 Jan, 2013 2 commits
  26. 19 Jan, 2013 1 commit
    • guiquanz's avatar
      Fixed many typos. · 1caf0939
      guiquanz authored
      Conflicts fixed, mainly because 2.8 has no cluster support / files:
      	00-RELEASENOTES
      	src/cluster.c
      	src/crc16.c
      	src/redis-trib.rb
      	src/redis.h
      1caf0939
  27. 14 Dec, 2012 1 commit
    • antirez's avatar
      serverCron() frequency is now a runtime parameter (was REDIS_HZ). · a6d117b6
      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.
      a6d117b6
  28. 31 Aug, 2012 1 commit
  29. 21 Apr, 2012 2 commits
    • antirez's avatar
      Limit memory used by big SLOWLOG entries. · 590d55a2
      antirez authored
      Two limits are added:
      
      1) Up to SLOWLOG_ENTRY_MAX_ARGV arguments are logged.
      2) Up to SLOWLOG_ENTRY_MAX_STRING bytes per argument are logged.
      3) slowlog-max-len is set to 128 by default (was 1024).
      
      The number of remaining arguments / bytes is logged in the entry
      so that the user can understand better the nature of the logged command.
      590d55a2
    • antirez's avatar
      redis.conf AOF section comments improved. · c11a01a0
      antirez authored
      c11a01a0