1. 06 May, 2019 2 commits
    • antirez's avatar
      6f4f36c0
    • antirez's avatar
      Threaded IO: implement handleClientsWithPendingWritesUsingThreads(). · f468e653
      antirez authored
      This is just an experiment for now, there are a couple of race
      conditions, mostly harmless for the performance gain experiment that
      this commit represents so far.
      
      The general idea here is to take Redis single threaded and instead
      fan-out on expansive kernel calls: write(2) in this case, but the same
      concept could be easily implemented for read(2) and protcol parsing.
      
      However just threading writes like in this commit, is enough to evaluate
      if the approach is sounding.
      f468e653
  2. 20 Mar, 2019 1 commit
  3. 18 Mar, 2019 1 commit
  4. 03 Mar, 2019 1 commit
  5. 27 Feb, 2019 1 commit
  6. 25 Feb, 2019 1 commit
  7. 21 Feb, 2019 1 commit
  8. 13 Feb, 2019 2 commits
    • zhaozhao.zz's avatar
      ACL: show categories in COMMAND reply · 14507457
      zhaozhao.zz authored
      Adding another new filed categories at the end of
      command reply, it's easy to read and distinguish
      flags and categories, also compatible with old format.
      14507457
    • antirez's avatar
      ACL: tag LASTSAVE as dangerous. · e819c2ef
      antirez authored
      That's not REALLY needed, but... right now with LASTSAVE being the only
      command tagged as "admin" but not "dangerous" what happens is that after
      rewrites the rewrite engine will produce from the rules:
      
          user default on +@all ~* -@dangerous nopass
      
      The rewrite:
      
          user default on nopass ~* +@all -@admin -@dangerous +lastsave
      
      Which is correct but will have users wondering about why LASTSAVE has
      something special.
      
      Since LASTSAVE after all also leaks information about the underlying
      server configuration, that may not be great for SAAS vendors, let's tag
      it as dangerous as well and forget about this issue :-)
      e819c2ef
  9. 12 Feb, 2019 1 commit
  10. 11 Feb, 2019 1 commit
  11. 07 Feb, 2019 1 commit
  12. 05 Feb, 2019 1 commit
  13. 04 Feb, 2019 1 commit
  14. 23 Jan, 2019 4 commits
  15. 22 Jan, 2019 4 commits
  16. 21 Jan, 2019 1 commit
  17. 18 Jan, 2019 1 commit
  18. 17 Jan, 2019 2 commits
  19. 16 Jan, 2019 1 commit
  20. 15 Jan, 2019 3 commits
  21. 14 Jan, 2019 2 commits
  22. 11 Jan, 2019 2 commits
  23. 10 Jan, 2019 1 commit
  24. 09 Jan, 2019 4 commits