From: "Shawn O. Pearce" <spearce@spearce.org>
To: Eric Wong <normalperson@yhbt.net>
Cc: Mike Hommey <mh@glandium.org>, git@vger.kernel.org
Subject: Re: Significant performance waste in git-svn and friends
Date: Fri, 7 Sep 2007 00:55:57 -0400 [thread overview]
Message-ID: <20070907045557.GY18160@spearce.org> (raw)
In-Reply-To: <20070906070407.GA19624@soma>
Eric Wong <normalperson@yhbt.net> wrote:
> Making git-svn use fast-import would be very nice. I've got a bunch
> of other git-svn things that I need to work on, but having git-svn
> converted to use fast-import would be nice. Or allowing Git.pm
> to access more of the git internals...
>
> However, how well/poorly would fast-import work for incremental
> fetches throughout the day?
It would work just fine. git-p4 uses fast-import and runs it in
incremental mode all of the time.
What will happen is you will get a packfile per git-svn fetch, so
if you fetch 5 times that day you will get 5 packfiles that day.
But you could also get 5 packfiles from git-fetch if each of those
fetches brought in 100 or more new objects. So it really is not
that big of a deal.
At some point the number of packfiles gets out of control, but so
does the number of loose objects. Repacking is the obvious fix in
both cases.
--
Shawn.
next prev parent reply other threads:[~2007-09-07 4:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 18:47 Significant performance waste in git-svn and friends Mike Hommey
2007-09-05 20:40 ` Junio C Hamano
2007-09-05 21:19 ` David Kastrup
2007-09-06 1:07 ` Patrick Doyle
2007-09-06 2:19 ` Shawn O. Pearce
2007-09-06 2:16 ` Shawn O. Pearce
2007-09-06 5:52 ` Mike Hommey
2007-09-06 7:04 ` Eric Wong
2007-09-07 4:55 ` Shawn O. Pearce [this message]
2007-09-07 6:28 ` Steven Grimm
2007-09-07 5:41 ` Mike Hommey
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=20070907045557.GY18160@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mh@glandium.org \
--cc=normalperson@yhbt.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).