- 15 9月, 2016 1 次提交
-
-
由 antirez 提交于
-
- 14 9月, 2016 4 次提交
-
-
由 antirez 提交于
What they say about "naming things" in programming?
-
由 antirez 提交于
-
由 antirez 提交于
Optimizations suggested and originally implemented by @oranagra. Re-applied by @antirez using the modified API.
-
由 oranagra 提交于
Notes by @antirez: This patch was picked from a larger commit by Oran and adapted to change the API a bit. The basic idea is to avoid double lookups when there is to use the value of the deleted entry. BEFORE: entry = dictFind( ... ); /* 1st lookup. */ /* Do somethjing with the entry. */ dictDelete(...); /* 2nd lookup. */ AFTER: entry = dictUnlink( ... ); /* 1st lookup. */ /* Do somethjing with the entry. */ dictFreeUnlinkedEntry(entry); /* No lookups!. */
-
- 13 9月, 2016 2 次提交
-
-
由 antirez 提交于
This code was extracted from @oranagra PR #3223 and modified in order to provide only certain amounts of information compared to the original code. It was also moved from DEBUG to the newly introduced MEMORY command. Thanks to Oran for the implementation and the PR. It implements detailed memory usage stats that can be useful in both provisioning and troubleshooting memory usage in Redis.
-
由 antirez 提交于
For most tasks, we need the memory estimation to be O(1) by default. This commit also implements an initial MEMORY command. Note that objectComputeSize() takes the number of samples to check as argument, so MEMORY should be able to get the sample size as option to make precision VS CPU tradeoff tunable. Related to: PR #3223.
-
- 12 9月, 2016 2 次提交
- 09 9月, 2016 9 次提交
- 08 9月, 2016 1 次提交
-
-
由 oranagra 提交于
-
- 07 9月, 2016 6 次提交
- 01 9月, 2016 2 次提交
-
-
由 antirez 提交于
Technically as soon as Redis 64 bit gets proper support for loading collections and/or DBs with more than 2^32 elements, the 32 bit version should be modified in order to check if what we read from rdbLoadLen() overflows. This would only apply to huge RDB files created with a 64 bit instance and later loaded into a 32 bit instance.
-
由 antirez 提交于
-
- 24 8月, 2016 2 次提交
- 12 8月, 2016 1 次提交
-
-
由 antirez 提交于
-
- 11 8月, 2016 2 次提交
- 09 8月, 2016 2 次提交
- 05 8月, 2016 1 次提交
-
-
由 Salvatore Sanfilippo 提交于
Display the nodes' proper summary once the cluster is created using redis-trib
-
- 04 8月, 2016 4 次提交
-
-
由 Salvatore Sanfilippo 提交于
Use the standard predefined identifier __func__ (since C99)
-
由 Guo Xiao 提交于
Fix warning: ISO C does not support '__FUNCTION__' predefined identifier [-Wpedantic]
-
由 antirez 提交于
-
由 antirez 提交于
After all crashing at every API misuse makes everybody's life more complex.
-
- 03 8月, 2016 1 次提交
-
-
由 antirez 提交于
This is an attempt at mitigating problems due to cross protocol scripting, an attack targeting services using line oriented protocols like Redis that can accept HTTP requests as valid protocol, by discarding the invalid parts and accepting the payloads sent, for example, via a POST request. For this to be effective, when we detect POST and Host: and terminate the connection asynchronously, the networking code was modified in order to never process further input. It was later verified that in a pipelined request containing a POST command, the successive commands are not executed.
-