git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Peter Harris <git@peter.is-a-geek.org>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org
Subject: Re: git and multiple cores
Date: Tue, 02 Jun 2009 19:54:03 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0906021949410.3906@xanadu.home> (raw)
In-Reply-To: <4A25B5C3.40409@nortel.com>

On Tue, 2 Jun 2009, Chris Friesen wrote:

> Peter Harris wrote:
> > On Tue, Jun 2, 2009 at 7:02 PM, Shawn O. Pearce wrote:
> > 
> >>True, but he was talking about initial clone, which on the client
> >>side is git-index-pack.  Which is not threaded.
> > 
> > 
> > Ah. I thought he was talking about the server side. My mistake.
> 
> Sorry, I wasn't clear.  I was talking about the client side, although
> the server side information is useful to have.
> 
> I have a 4-way machine as a client, and it just seemed odd that git
> could only use one core.

It can use them all when repacking or pushing.  But on a clone or fetch 
your client machine deals with incoming data using index-pack which is 
much more trickier to thread.


Nicolas

      reply	other threads:[~2009-06-02 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 22:40 git and multiple cores Chris Friesen
2009-06-02 22:55 ` Peter Harris
2009-06-02 23:02   ` Shawn O. Pearce
2009-06-02 23:12     ` Peter Harris
2009-06-02 23:29       ` Chris Friesen
2009-06-02 23:54         ` Nicolas Pitre [this message]

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=alpine.LFD.2.00.0906021949410.3906@xanadu.home \
    --to=nico@cam.org \
    --cc=cfriesen@nortel.com \
    --cc=git@peter.is-a-geek.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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.
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).