From: Nicolas Pitre <nico@cam.org>
To: Sean <seanlkml@sympatico.ca>
Cc: keithp@keithp.com, git@vger.kernel.org
Subject: Re: observations on parsecvs testing
Date: Thu, 15 Jun 2006 16:55:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606151653440.16002@localhost.localdomain> (raw)
In-Reply-To: <BAYC1-PASMTP10021C1A6034B8753D06DDAE820@CEZ.ICE>
On Thu, 15 Jun 2006, Sean wrote:
> On Thu, 15 Jun 2006 16:37:30 -0400 (EDT)
> Nicolas Pitre <nico@cam.org> wrote:
>
> > Also rcs2git() is very inefficient especially with files having many
> > revisions as it reconstructs the delta chain on every call. For example
> > mozilla/configure,v has at least 1690 revisions, and actually converting
> > it into GIT blobs goes at a rate of 2.4 objects per second _only_ on my
> > machine. Can't objects be created as the delta list is walked/applied
> > instead? That would significantly reduce the initial convertion time.
>
> Hi Nicolas,
>
> That was a planned optimization which I did mention to Keith previously.
> Was kinda waiting to hear back how it was working for him, and if there
> was an interest to put more work into it to include in his mainline.
I think it is really worth it. I'd expect the first half of the
convertion to go significantly faster then.
Nicolas
next prev parent reply other threads:[~2006-06-15 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 20:37 observations on parsecvs testing Nicolas Pitre
[not found] ` <20060615164742.570e33a0.seanlkml@sympatico.ca>
2006-06-15 20:47 ` Sean
2006-06-15 20:55 ` Nicolas Pitre [this message]
2006-06-15 22:04 ` Keith Packard
2006-06-15 22:03 ` Keith Packard
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=Pine.LNX.4.64.0606151653440.16002@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=keithp@keithp.com \
--cc=seanlkml@sympatico.ca \
/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).