git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: parsecvs fails even on simple input

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jun 25, 2007, 04:59 UTC
Message-ID
<20070625045951.GB32223@spearce.org>
In-Reply-To
<1182720667.13289.41.camel@neko.keithp.com>
Keith Packard <keithp@keithp.com> wrote:
Show 5 quoted lines
> 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.
Previous: Keith PackardNext: Roman Kagan
Message 3 of 5 in “parsecvs fails even on simple input”
  1. Roman KaganJun 22, 2007
  2. Keith PackardJun 24, 2007
  3. Shawn O. PearceJun 25, 2007
  4. Roman KaganJun 27, 2007
  5. Keith PackardJun 27, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.