Git development
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@buug.org>
To: git@vger.kernel.org
Subject: fast-import: multiple processes possible?
Date: Sat, 27 Nov 2010 14:07:45 -0800	[thread overview]
Message-ID: <8739qmzaha.fsf@matica.localdomain> (raw)


Hi, I have a user question, I hope that's ok.  Actually, the end goal is
development of a fast-import frontend.  The fast-import manpage says
that it is safe to run "any other" git operation concurrently with
fast-import.  It doesn't say if it is possible and safe to run another
copy of fast-import itself.

The reason I'd like to do this is speedup.  With sequential approach my
frontend can only load each core on my system about 50%.  If I could run
multiple imports concurrently I could make it close to 100%, especially
when feeding it blobs (which take most of the time).

Thanks for the advice.

-- 
Ian Zimmerman <itz@buug.org>
gpg public key: 1024D/C6FF61AD 
fingerprint: 66DC D68F 5C1B 4D71 2EE5  BD03 8A00 786C C6FF 61AD
Ham is for reading, not for eating.

             reply	other threads:[~2010-11-27 22:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 22:07 Ian Zimmerman [this message]
2010-11-27 22:28 ` fast-import: multiple processes possible? Shawn Pearce

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=8739qmzaha.fsf@matica.localdomain \
    --to=itz@buug.org \
    --cc=git@vger.kernel.org \
    /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