From: Nicolas Pitre <nico@cam.org>
To: Brian Downing <bdowning@lavos.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 5/5] Add documentation for --window-bytes, pack.windowBytes
Date: Thu, 12 Jul 2007 00:35:22 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707120028020.32552@xanadu.home> (raw)
In-Reply-To: <1184210058514-git-send-email-bdowning@lavos.net>
On Wed, 11 Jul 2007, Brian Downing wrote:
> 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.
> +
This doesn't say what the default (unlimited) is.
> 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.
Ditto here.
Also it is a bit akward to specify a size in bytes when you probably
want to specify a limit which is in the megabyte range. I'd call them
--window_mem and pack.windowmemory, and allow for unit suffixes of 'k',
'm', or 'g' to be supported if not already.
Nicolas
next prev parent reply other threads:[~2007-07-12 4:35 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 ` [PATCH 5/5] Add documentation for --window-bytes, pack.windowBytes Brian Downing
2007-07-12 4:35 ` Nicolas Pitre [this message]
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=alpine.LFD.0.999.0707120028020.32552@xanadu.home \
--to=nico@cam.org \
--cc=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).