From: "Chris Friesen" <cfriesen@nortel.com>
To: Peter Harris <git@peter.is-a-geek.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: git and multiple cores
Date: Tue, 02 Jun 2009 17:29:07 -0600 [thread overview]
Message-ID: <4A25B5C3.40409@nortel.com> (raw)
In-Reply-To: <eaa105840906021612y5b9e4c25o1062d7f7aecfbd16@mail.gmail.com>
Peter Harris wrote:
> On Tue, Jun 2, 2009 at 7:02 PM, Shawn O. Pearce wrote:
>
>>Peter Harris <git@peter.is-a-geek.org> wrote:
>>
>>>On Tue, Jun 2, 2009 at 6:40 PM, Chris Friesen wrote:
>>>
>>>>I'm using git 1.6.1.3 and it seems to be limited to a single core.
>>>>Given that I've seen cases where the cpu has been basically pinned for
>>>>minutes on end (initial clone of a repository, for instance) has there
>>>>been any discussion of taking advantage of multiple cores?
>>>
>>>Sounds like you're mostly concerned about packing.
>>>
>>>The good news is, your version of git already has a threaded packer.
>>>You just need to enable it. See "pack.threads" in "git help config".
>>>
>>>1.6.2 and newer use multiple threads by default.
>>
>>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.
Chris
next prev parent reply other threads:[~2009-06-02 23:29 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 [this message]
2009-06-02 23:54 ` Nicolas Pitre
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=4A25B5C3.40409@nortel.com \
--to=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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.