- 09 Oct, 2015 1 commit
- 
- 
antirez authored
 
- 
- 07 Oct, 2015 3 commits
- 
- 
antirez authored
- 
antirez authoredthe check for lat/long valid ranges were performed inside the for loop, two times instead of one, and the first time when the second element of the array, xy[1], was yet not populated. This resulted into issue #2799. Close issue #2799. 
- 
antirez authoredNow way to make unmodified Jemalloc configure to work when the jemalloc source tree is inside a subdirectory of a different git repository. Problem signaled here: http://www.canonware.com/pipermail/jemalloc-discuss/2015-October/001174.html 
 
- 
- 06 Oct, 2015 4 commits
- 05 Oct, 2015 2 commits
- 02 Oct, 2015 1 commit
- 
- 
antirez authored
 
- 
- 01 Oct, 2015 24 commits
- 
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authoredWe have them into zmalloc.c, but this is going to replace that implementation, so that it's possible to use the same idea everywhere inside the code base. 
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
- 
antirez authored
 
- 
- 30 Sep, 2015 5 commits
- 
- 
antirez authored
- 
antirez authoredAfter the introduction of the list with clients with pending writes, to process clients incrementally outside of the event loop we also need to process the pending writes list. 
- 
antirez authored
- 
antirez authored
- 
antirez authoredMay potentially improve locality... not exactly clear if this makes a difference or not. But for sure is harmless. 
 
-