1. 01 Jul, 2018 1 commit
  2. 25 May, 2018 1 commit
  3. 24 May, 2018 1 commit
  4. 17 May, 2018 1 commit
    • Oran Agra's avatar
      Active defrag fixes for 32bit builds · ad133e10
      Oran Agra authored
      problems fixed:
      * failing to read fragmentation information from jemalloc
      * overflow in jemalloc fragmentation hint to the defragger
      * test suite not triggering eviction after population
      ad133e10
  5. 15 May, 2018 2 commits
  6. 11 May, 2018 2 commits
  7. 29 Apr, 2018 1 commit
  8. 23 Apr, 2018 1 commit
  9. 20 Apr, 2018 1 commit
  10. 25 Mar, 2018 1 commit
  11. 15 Mar, 2018 6 commits
  12. 14 Mar, 2018 1 commit
  13. 12 Mar, 2018 1 commit
    • Oran Agra's avatar
      Adding real allocator fragmentation to INFO and MEMORY command + active defrag test · 806736cd
      Oran Agra authored
      other fixes / improvements:
      - LUA script memory isn't taken from zmalloc (taken from libc malloc)
        so it can cause high fragmentation ratio to be displayed (which is false)
      - there was a problem with "fragmentation" info being calculated from
        RSS and used_memory sampled at different times (now sampling them together)
      
      other details:
      - adding a few more allocator info fields to INFO and MEMORY commands
      - improve defrag test to measure defrag latency of big keys
      - increasing the accuracy of the defrag test (by looking at real grag info)
        this way we can use an even lower threshold and still avoid false positives
      - keep the old (total) "fragmentation" field unchanged, but add new ones for spcific things
      - add these the MEMORY DOCTOR command
      - deduct LUA memory from the rss in case of non jemalloc allocator (one for which we don't "allocator active/used")
      - reduce sampling rate of the rss and allocator info
      806736cd
  14. 24 Jan, 2018 1 commit
  15. 09 Jan, 2018 1 commit
  16. 04 Dec, 2017 1 commit
  17. 01 Dec, 2017 9 commits
  18. 30 Nov, 2017 1 commit
  19. 24 Nov, 2017 1 commit
  20. 23 Nov, 2017 1 commit
    • Oran Agra's avatar
      fix string to double conversion, stopped parsing on \0 even if the string has more data. · adf2701c
      Oran Agra authored
      getLongLongFromObject calls string2ll which has this line:
      /* Return if not all bytes were used. */
      so if you pass an sds with 3 characters "1\01" it will fail.
      
      but getLongDoubleFromObject calls strtold, and considers it ok if eptr[0]==`\0`
      i.e. if the end of the string found by strtold ends with null terminator
      
      127.0.0.1:6379> set a 1
      OK
      127.0.0.1:6379> setrange a 2 2
      (integer) 3
      127.0.0.1:6379> get a
      "1\x002"
      127.0.0.1:6379> incrbyfloat a 2
      "3"
      127.0.0.1:6379> get a
      "3"
      adf2701c
  21. 30 Oct, 2017 1 commit
  22. 13 Aug, 2017 1 commit
  23. 03 Jul, 2017 1 commit
    • antirez's avatar
      Fix GEORADIUS edge case with huge radius. · b2cd9fca
      antirez authored
      This commit closes issue #3698, at least for now, since the root cause
      was not fixed: the bounding box function, for huge radiuses, does not
      return a correct bounding box, there are points still within the radius
      that are left outside.
      
      So when using GEORADIUS queries with radiuses in the order of 5000 km or
      more, it was possible to see, at the edge of the area, certain points
      not correctly reported.
      
      Because the bounding box for now was used just as an optimization, and
      such huge radiuses are not common, for now the optimization is just
      switched off when the radius is near such magnitude.
      
      Three test cases found by the Continuous Integration test were added, so
      that we can easily trigger the bug again, both for regression testing
      and in order to properly fix it as some point in the future.
      b2cd9fca
  24. 16 Jun, 2017 1 commit
  25. 15 Jun, 2017 1 commit