- 02 Aug, 2018 5 commits
- 30 Jul, 2018 13 commits
-
-
Guy Korland authored
-
antirez authored
User: "is there a reason why redis server logs are missing the year in the "date time"?" Me: "I guess I did not imagine it would be stable enough to run for several years".
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This way we can remember what the user configured HZ is, but change the actual HZ dynamically if needed in the dynamic HZ feature implementation.
-
antirez authored
Related to #4852.
-
antirez authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
antirez authored
Related to #5154.
-
antirez authored
-
WuYunlong authored
-
- 25 Jul, 2018 1 commit
-
-
Pavel Rochnyack authored
Closes: #5033
-
- 24 Jul, 2018 8 commits
-
-
antirez authored
After #5161 the code could be made a bit more obvious for newcomers.
-
zhaozhao.zz authored
-
antirez authored
-
dsomeshwar authored
-
antirez authored
See PR #5157.
-
Oran Agra authored
-
antirez authored
Related to #5157. The PR author correctly indentified that the check was duplicated, but removing the second one introduces a bug that was fixed in the past (hence the duplication). Instead we can remove the first instance of the check without issues.
-
antirez authored
-
- 23 Jul, 2018 4 commits
-
-
antirez authored
Related to #4883.
-
Itamar Haber authored
-
Itamar Haber authored
Implementation notes: as INFO is "already broken", I didn't want to break it further. Instead of computing the server.lua_script dict size on every call, I'm keeping a running sum of the body's length and dict overheads. This implementation is naive as it **does not** take into consideration dict rehashing, but that inaccuracy pays off in speed ;) Demo time: ```bash $ redis-cli info memory | grep "script" used_memory_scripts:96 used_memory_scripts_human:96B number_of_cached_scripts:0 $ redis-cli eval "" 0 ; redis-cli info memory | grep "script" (nil) used_memory_scripts:120 used_memory_scripts_human:120B number_of_cached_scripts:1 $ redis-cli script flush ; redis-cli info memory | grep "script" OK used_memory_scripts:96 used_memory_scripts_human:96B number_of_cached_scripts:0 $ redis-cli eval "return('Hello, Script Cache :)')" 0 ; redis-cli info memory | grep "script" "Hello, Script Cache :)" used_memory_scripts:152 used_memory_scripts_human:152B number_of_cached_scripts:1 $ redis-cli eval "return redis.sha1hex(\"return('Hello, Script Cache :)')\")" 0 ; redis-cli info memory | grep "script" "1be72729d43da5114929c1260a749073732dc822" used_memory_scripts:232 used_memory_scripts_human:232B number_of_cached_scripts:2
✔ 19:03:54 redis [lua_scripts-in-info-memory L ✚…⚑] $ redis-cli evalsha 1be72729d43da5114929c1260a749073732dc822 0 "Hello, Script Cache :)" ``` -
antirez authored
For some reason I made a merge fiasco between 5.0 and unstable. This fixes the error introduced by merging unstable.
-
- 20 Jul, 2018 2 commits
- 19 Jul, 2018 7 commits