From: Brian Downing <bdowning@lavos.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Brian Downing <bdowning@lavos.net>
Subject: [PATCH 5/5] Add documentation for --window-bytes, pack.windowBytes
Date: Wed, 11 Jul 2007 22:14:18 -0500 [thread overview]
Message-ID: <1184210058514-git-send-email-bdowning@lavos.net> (raw)
In-Reply-To: <11842100581060-git-send-email-bdowning@lavos.net>
Signed-off-by: Brian Downing <bdowning@lavos.net>
---
Documentation/config.txt | 5 +++++
Documentation/git-pack-objects.txt | 8 ++++++++
Documentation/git-repack.txt | 8 ++++++++
3 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index aeece84..83c7dc1 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -592,6 +592,11 @@ pack.depth::
The maximum delta depth used by gitlink:git-pack-objects[1] when no
maximum depth is given on the command line. Defaults to 50.
+pack.windowBytes::
+ This option provides an additional limit on top of `pack.window`;
+ the window size will dynamically scale down so as to not take
+ up more than N bytes in memory.
+
pack.compression::
An integer -1..9, indicating the compression level for objects
in a pack file. -1 is the zlib default. 0 means no
diff --git a/Documentation/git-pack-objects.txt b/Documentation/git-pack-objects.txt
index e3549b5..21ed198 100644
--- a/Documentation/git-pack-objects.txt
+++ b/Documentation/git-pack-objects.txt
@@ -85,6 +85,14 @@ base-name::
times to get to the necessary object.
The default value for --window is 10 and --depth is 50.
+--window-bytes=[N]::
+ This option provides an additional limit on top of `--window`;
+ the window size will dynamically scale down so as to not take
+ up more than N bytes in memory. This is useful in
+ repositories with a mix of large and small objects to not run
+ out of memory with a large window, but still be able to take
+ advantage of the large window for the smaller objects.
+
--max-pack-size=<n>::
Maximum size of each output packfile, expressed in MiB.
If specified, multiple packfiles may be created.
diff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt
index 2894939..805d930 100644
--- a/Documentation/git-repack.txt
+++ b/Documentation/git-repack.txt
@@ -68,6 +68,14 @@ OPTIONS
to be applied that many times to get to the necessary object.
The default value for --window is 10 and --depth is 50.
+--window-bytes=[N]::
+ This option provides an additional limit on top of `--window`;
+ the window size will dynamically scale down so as to not take
+ up more than N bytes in memory. This is useful in
+ repositories with a mix of large and small objects to not run
+ out of memory with a large window, but still be able to take
+ advantage of the large window for the smaller objects.
+
--max-pack-size=<n>::
Maximum size of each output packfile, expressed in MiB.
If specified, multiple packfiles may be created.
--
1.5.2.GIT
next prev parent reply other threads:[~2007-07-12 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 3:14 [PATCH 0/5] Memory-limited pack-object window support Brian Downing
2007-07-12 3:14 ` [PATCH 1/5] Don't try to delta if target is much smaller than source Brian Downing
2007-07-12 3:14 ` [PATCH 2/5] Support fetching the memory usage of a delta index Brian Downing
2007-07-12 3:14 ` [PATCH 3/5] Add pack-objects window memory usage limit Brian Downing
2007-07-12 4:25 ` Nicolas Pitre
2007-07-12 10:02 ` Brian Downing
2007-07-12 3:14 ` [PATCH 4/5] Add --window-bytes option to git-repack Brian Downing
2007-07-12 3:14 ` Brian Downing [this message]
2007-07-12 4:35 ` [PATCH 5/5] Add documentation for --window-bytes, pack.windowBytes Nicolas Pitre
2007-07-12 4:38 ` [PATCH 0/5] Memory-limited pack-object window support Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1184210058514-git-send-email-bdowning@lavos.net \
--to=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).