antirez
ca734d17ad
Revert "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."
...
This reverts commit a3e60027e7d4419971406c6da7d6e8accbcaf9b0.
2010-11-02 12:09:59 +01:00
antirez
a3e60027e7
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.
2010-11-02 11:50:55 +01:00
Pieter Noordhuis
56e52b69fe
Update rdb.c to properly work with new memory strategy for sorted sets
2010-09-22 18:07:52 +02:00
antirez
2f6b31c3bb
Fix for a race in BGSAVE that may result in some data not being saved as soon as possible (when the configured saving triggers should fire). Also known as Issue 313, more details there in the google code issue.
2010-08-30 10:32:32 +02:00
antirez
2df84b7269
intset loading bug fixed
2010-08-26 19:10:40 +02:00
antirez
23c64fe50d
translated a few long logn into int64_t for correctness and to avoid compilation warnings as well
2010-08-26 18:11:26 +02:00
antirez
bad7d097e9
fixed a memory leak in the new Set code
2010-08-26 13:18:24 +02:00
Pieter Noordhuis
96ffb2fe97
merged intset code into the split files
2010-07-02 19:57:12 +02:00
antirez
3688d7f308
Compilation fixed on Linux after the source code split
2010-07-01 21:13:38 +02:00
antirez
e2641e09cc
redis.c split into many different C files.
...
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
2010-07-01 14:38:51 +02:00
