Sat, 07 Aug 2010 12:55:30 +0800 minor style fix: hgext/rebase.py:157 -- line too long
Alecs King <alecsk@gmail.com> [Sat, 07 Aug 2010 12:55:30 +0800] rev 11761
minor style fix: hgext/rebase.py:157 -- line too long found by a run of check-code
Sat, 07 Aug 2010 15:32:33 +0900 zsh completions: add qpush --move option
Yuya Nishihara <yuya@tcha.org> [Sat, 07 Aug 2010 15:32:33 +0900] rev 11760
zsh completions: add qpush --move option
Fri, 06 Aug 2010 12:59:13 -0500 Merge with stable
Matt Mackall <mpm@selenic.com> [Fri, 06 Aug 2010 12:59:13 -0500] rev 11759
Merge with stable
Fri, 06 Aug 2010 12:18:33 -0500 chunkbuffer: use += rather than cStringIO to reduce memory footprint stable
Matt Mackall <mpm@selenic.com> [Fri, 06 Aug 2010 12:18:33 -0500] rev 11758
chunkbuffer: use += rather than cStringIO to reduce memory footprint This significantly refactors the read() loop to use a queue of chunks. The queue is alternately filled to at least 256k and then emptied by concatenating onto the output buffer. For very large read sizes, += uses less memory because it can resize the target string in place.
Thu, 05 Aug 2010 16:17:39 -0500 httprepo: decompress stream incrementally to reduce memory usage stable
Matt Mackall <mpm@selenic.com> [Thu, 05 Aug 2010 16:17:39 -0500] rev 11757
httprepo: decompress stream incrementally to reduce memory usage
Thu, 05 Aug 2010 16:17:33 -0500 verify: initialize rp variable in case we hit out of memory stable
Matt Mackall <mpm@selenic.com> [Thu, 05 Aug 2010 16:17:33 -0500] rev 11756
verify: initialize rp variable in case we hit out of memory
Thu, 05 Aug 2010 16:17:17 -0500 merge: drop reference to file contents after write stable
Matt Mackall <mpm@selenic.com> [Thu, 05 Aug 2010 16:17:17 -0500] rev 11755
merge: drop reference to file contents after write This reduces memory usage on large consecutive gets.
Thu, 05 Aug 2010 16:17:17 -0500 revlog: drop cache after use to save memory footprint stable
Matt Mackall <mpm@selenic.com> [Thu, 05 Aug 2010 16:17:17 -0500] rev 11754
revlog: drop cache after use to save memory footprint If we reconstruct back to back large versions, we need to drop the cache first to avoid doubling memory usage.
Thu, 05 Aug 2010 16:17:17 -0500 verify: reduce memory footprint when unpacking files stable
Matt Mackall <mpm@selenic.com> [Thu, 05 Aug 2010 16:17:17 -0500] rev 11753
verify: reduce memory footprint when unpacking files By never holding a reference to the unpacked string, we avoid holding two consecutive large files in memory.
Thu, 05 Aug 2010 16:17:17 -0500 verify: report exceptions that don't have a str() method stable
Matt Mackall <mpm@selenic.com> [Thu, 05 Aug 2010 16:17:17 -0500] rev 11752
verify: report exceptions that don't have a str() method
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip