summaryrefslogtreecommitdiff
path: root/src/zmalloc.c
Commit message (Collapse)AuthorAgeFilesLines
* use gcc sync builtins for memory counter when possiblePremysl Hruby2012-02-261-9/+33
|
* Precision of getClientOutputBufferMemoryUsage() greatily improved, see issue ↵antirez2012-02-071-0/+14
| | | | #327 for more information.
* Fix crash on SPARC due to improper alignment of allocated memoryChris Lamb2011-11-161-1/+1
| | | | | | | | | | 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: Chris Lamb <lamby@debian.org>
* no more allocation stats info in INFO, useless now that we have jemalloc.antirez2011-07-021-10/+0
|
* forward-ported changes in zmalloc.c/h to support jemalloc buildantirez2011-06-201-5/+10
|
* Fixed compilation on FreeBSDantirez2011-01-201-1/+1
|
* initial fix of the test suite to run both in in-memory and diskstore modeantirez2011-01-091-1/+1
|
* allocation stats in INFOantirez2011-01-091-12/+23
|
* zmalloc functions to get RSS and fragmentation refactored into two separated ↵antirez2010-11-021-8/+25
| | | | functions
* Don't use prefix when malloc_size() can be calledPieter Noordhuis2010-10-231-3/+14
| | | | | Also, use tcmalloc functions explicitly via macros to prevent symbol lookups to resolve to native malloc/free on OSX.
* memory fragmentation reporting in INFO also added for Mac OS Xantirez2010-09-021-6/+31
|
* memory fragmentation ratio in INFO outputantirez2010-09-021-0/+42
|
* Add zcalloc and use it where appropriateBenjamin Kramer2010-07-251-0/+14
| | | | | | | | | | | | | 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.
* redis.c split into many different C files.antirez2010-07-011-0/+158
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