summaryrefslogtreecommitdiff
path: root/local-fetch.c
diff options
context:
space:
mode:
authorLibravatar Shawn O. Pearce <spearce@spearce.org>2006-12-24 00:47:19 -0500
committerLibravatar Junio C Hamano <junkio@cox.net>2006-12-29 11:36:45 -0800
commit97bfeb34df1aa8a1cf232278624a5a5c924ee380 (patch)
treec1591e0eac89204f6db3f2a8a8ec3b86b6c40be1 /local-fetch.c
parentDefault core.packdGitWindowSize to 1 MiB if NO_MMAP. (diff)
downloadtgif-97bfeb34df1aa8a1cf232278624a5a5c924ee380.tar.xz
Release pack windows before reporting out of memory.
If we are about to fail because this process has run out of memory we should first try to automatically control our appetite for address space by releasing enough least-recently-used pack windows to gain back enough memory such that we might actually be able to meet the current allocation request. This should help users who have fairly large repositories but are working on systems with relatively small virtual address space. Many times we see reports on the mailing list of these users running out of memory during various Git operations. Dynamically decreasing the amount of pack memory used when the demand for heap memory is increasing is an intelligent solution to this problem. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'local-fetch.c')
0 files changed, 0 insertions, 0 deletions