From: Eric Wong <normalperson@yhbt.net>
To: "Gunnlaugur Þór Briem" <gunnlaugur@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] Document git-svn fetch --log-window-size parameter
Date: Fri, 26 Oct 2012 09:46:02 +0000 [thread overview]
Message-ID: <20121026094602.GA7887@dcvr.yhbt.net> (raw)
In-Reply-To: <20121025095202.GK8390@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> On Tue, Oct 23, 2012 at 10:33:26AM +0000, Gunnlaugur Þór Briem wrote:
>
> > The --log-window-size parameter to git-svn fetch is undocumented.
> >
> > Minimally describe what it does and why the user might change it.
>
> Thanks. Your description makes sense to me, but I do not have enough
> git-svn knowledge to know if it covers all intended uses of the flag.
> Eric?
>
> > +--log-window-size=<n>;;
> > + Fetch <n> log entries per request when scanning Subversion history.
> > + The default is 100. For very large Subversion repositories, larger
> > + values may be needed for 'clone'/'fetch' to complete in reasonable
> > + time. But overly large values may lead to request timeouts.
Overly large values also lead to excessive memory usage. I may have
only had 256M in my dev machine at the time I added this parameter:
commit 6af1db447b10c03db4c04a55000efaa9aad38caa
Author: Eric Wong <normalperson@yhbt.net>
Date: Wed Feb 14 16:04:10 2007 -0800
git-svn: allow --log-window-size to be specified, default to 100
The newer default value should should lower memory usage for
large fetches and also help with fetching from less reliable
servers. Previously the value was 1000 and memory usage
got a bit high on some repositories and fetching became
less reliable in some cases.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
next prev parent reply other threads:[~2012-10-26 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 10:33 [PATCH] Document git-svn fetch --log-window-size parameter Gunnlaugur Þór Briem
2012-10-25 9:52 ` Jeff King
2012-10-26 9:46 ` Eric Wong [this message]
2012-10-26 13:32 ` Jeff King
2012-10-26 13:45 ` Gunnlaugur Thor Briem
2012-10-29 20:18 ` Eric Wong
2012-10-29 22:02 ` Jeff King
2012-10-29 22:36 ` Eric Wong
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121026094602.GA7887@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=gunnlaugur@gmail.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).