- 24 8月, 2012 2 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
The previous implementation of zmalloc.c was not able to handle out of memory in an application-specific way. It just logged an error on standard error, and aborted. The result was that in the case of an actual out of memory in Redis where malloc returned NULL (In Linux this actually happens under specific overcommit policy settings and/or with no or little swap configured) the error was not properly logged in the Redis log. This commit fixes this problem, fixing issue #509. Now the out of memory is properly reported in the Redis log and a stack trace is generated. The approach used is to provide a configurable out of memory handler to zmalloc (otherwise the default one logging the event on the standard output is used).
-
- 27 3月, 2012 2 次提交
- 26 2月, 2012 1 次提交
-
-
由 Premysl Hruby 提交于
-
- 07 2月, 2012 1 次提交
-
-
由 antirez 提交于
Precision of getClientOutputBufferMemoryUsage() greatily improved, see issue #327 for more information.
-
- 17 11月, 2011 1 次提交
-
-
由 Chris Lamb 提交于
I believe that you should be able to drop 'defined(__sun)' completely from this clause, as Solaris on x86 hardware probably does not have strict alignment requirements, but I don't have a way to test that. Thanks to Jurij Smakov <jurij@wooyd.org>. Signed-off-by: NChris Lamb <lamby@debian.org>
-
- 02 7月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 20 6月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 20 1月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 09 1月, 2011 2 次提交
- 02 11月, 2010 1 次提交
-
-
由 antirez 提交于
-
- 23 10月, 2010 1 次提交
-
-
由 Pieter Noordhuis 提交于
Also, use tcmalloc functions explicitly via macros to prevent symbol lookups to resolve to native malloc/free on OSX.
-
- 02 9月, 2010 2 次提交
- 25 7月, 2010 1 次提交
-
-
由 Benjamin Kramer 提交于
calloc is more effecient than malloc+memset when the system uses mmap to allocate memory. mmap always returns zeroed memory so the memset can be avoided. The threshold to use mmap is 16k in osx libc and 128k in bsd libc and glibc. The kernel can lazily allocate the pages, this reduces memory usage when we have a page table or hash table that is mostly empty. This change is most visible when you start a new redis instance with vm enabled. You'll see no increased memory usage no matter how big your page table is.
-
- 01 7月, 2010 1 次提交
-
-
由 antirez 提交于
networking related stuff moved into networking.c moved more code more work on layout of source code SDS instantaneuos memory saving. By Pieter and Salvatore at VMware ;) cleanly compiling again after the first split, now splitting it in more C files moving more things around... work in progress split replication code splitting more Sets split Hash split replication split even more splitting more splitting minor change
-
- 20 4月, 2010 1 次提交
-
-
由 antirez 提交于
-
- 19 2月, 2010 1 次提交
-
-
由 antirez 提交于
A problem with replication with multiple slaves connectiong to a single master fixed. It was due to a typo, and reported on github by the user micmac. Also the copyright year fixed from many files.
-
- 15 1月, 2010 1 次提交
-
-
由 antirez 提交于
-
- 11 1月, 2010 1 次提交
-
-
由 antirez 提交于
-
- 01 11月, 2009 1 次提交
-
-
由 antirez 提交于
-
- 27 10月, 2009 1 次提交
-
-
由 antirez 提交于
-
- 24 10月, 2009 1 次提交
-
-
由 antirez 提交于
initial skiplist implementation. Most memory checks removed and zmalloc() modified to fail with an error message and abort. Anyway Redis is not designed to recover from out of memory conditions.
-
- 05 6月, 2009 2 次提交
- 01 5月, 2009 1 次提交
-
-
由 antirez 提交于
-
- 28 3月, 2009 1 次提交
-
-
由 antirez 提交于
-
- 22 3月, 2009 1 次提交
-
-
由 antirez 提交于
-