From: "Shawn O. Pearce" <spearce@spearce.org>
To: Keith Packard <keithp@keithp.com>
Cc: Roman Kagan <rkagan@sw.ru>, Al Viro <viro@zeniv.linux.org.uk>,
git@vger.kernel.org
Subject: Re: parsecvs fails even on simple input
Date: Mon, 25 Jun 2007 00:59:51 -0400 [thread overview]
Message-ID: <20070625045951.GB32223@spearce.org> (raw)
In-Reply-To: <1182720667.13289.41.camel@neko.keithp.com>
Keith Packard <keithp@keithp.com> wrote:
> On Fri, 2007-06-22 at 15:36 +0400, Roman Kagan wrote:
> > Wouldn't it be better to teach parsecvs
> > to speak git-fast-import language instead?
>
> Avoiding fork/exec is rather important for parsecvs perforamance.
That sort of thing is the entire point behind fast-import. Its only
one fork+exec to setup the fast-import "daemon" in the background,
and you do everything over a pipe to its stdin. Including forcing
it to finish its current packfile and open a new one on the next
object (the `checkpoint` command).
fast-import is fast, its input language is fairly simple, and its
quite stable. And its only one fork+exec. That's peanuts compared
to the disk IO involved in any sizable import process.
--
Shawn.
next prev parent reply other threads:[~2007-06-25 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 11:36 parsecvs fails even on simple input Roman Kagan
2007-06-24 21:31 ` Keith Packard
2007-06-25 4:59 ` Shawn O. Pearce [this message]
2007-06-27 15:33 ` Roman Kagan
2007-06-27 17:20 ` 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=20070625045951.GB32223@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=keithp@keithp.com \
--cc=rkagan@sw.ru \
--cc=viro@zeniv.linux.org.uk \
/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).