[PATCH] Expand on impact of threads on memory consumption.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It took me a long time to notice the rider on the pack.threads
configuration option that it would multiple the memory consumption by
the number of CPUs in the machine. This patch puts the memory consumption
warning against the memory option that I was using to try to stop git-pack
running out of RAM.

Signed-off-by: Robert de Bath <rdebath@xxxxxxxxxxxxxxxxx>
---
 Documentation/config.txt |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index c55c22a..6384038 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1828,7 +1828,10 @@ pack.depth::
 
 pack.windowMemory::
 	The window memory size limit used by linkgit:git-pack-objects[1]
-	when no limit is given on the command line.  The value can be
+	when no limit is given on the command line.  This limit may be
+	allocated individually by each thread doing delta compression
+	so the total memory allocated by linkgit:git-pack-objects[1] can
+	be this multiplied by the number of threads.  The value can be
 	suffixed with "k", "m", or "g".  Defaults to 0, meaning no
 	limit.
 
-- 
1.7.10.4


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]