- 30 11月, 2010 1 次提交
-
-
- 29 11月, 2010 2 次提交
- 21 11月, 2010 4 次提交
-
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
Now the rdbSave* functions return the number of bytes written (or required to write) in serializing a Redis object, writing to /dev/null and using ftell (which doesn't work on FreeBSD) isn't needed anymore.
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
- 13 11月, 2010 1 次提交
-
-
由 antirez 提交于
-
- 11 11月, 2010 1 次提交
-
-
由 antirez 提交于
volatile-lru maxmemory policy segfault fixed, thanks to Anthony Lauzon for reporting the problem with the patch. Original patch modified a bit in order to avoid the double lookup if the policy is allkeys-lru
-
- 08 11月, 2010 6 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
added noeviction policy to redis maxmemory. ZSCORE removed from the list of commands that can't be called when we are low on memory, this command was added in the past for a stupid error.
-
由 antirez 提交于
build redis-server at the end so have a more pleasing to see Make output and the advice to run the test suite at the end.
-
由 antirez 提交于
-
由 antirez 提交于
-
- 05 11月, 2010 9 次提交
- 04 11月, 2010 6 次提交
-
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
由 Pieter Noordhuis 提交于
-
- 03 11月, 2010 7 次提交
-
-
由 Pieter Noordhuis 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
Now it is possible to use quoted strings in the redis.conf file accordingly to the sdssplitargs() function capabilities.
-
由 antirez 提交于
-
由 antirez 提交于
Do not update the LRU info on key lookup when we have a saving child. With this trivial change the additional memory used while saving with a background child in presence of many read operations is zero.
-
由 antirez 提交于
redis-cli in interactive mode now prints the time elapsed of the operation performed took more than half a second.
-
- 02 11月, 2010 3 次提交
-
-
由 antirez 提交于
Now maxmemory, VM, and everything else uses the fast RSS memory used estimation instead of raw memory reported by zmalloc(). This means that setting maxmemory to 2GB will really have the effect of using up to 2GB of memory.