Re: git and multiple cores

From: Chris Friesen <cfriesen@nortel.com>
Date: Jun 2, 2009, 23:29 UTC
Message-ID: <4A25B5C3.40409@nortel.com>
In-Reply-To: <eaa105840906021612y5b9e4c25o1062d7f7aecfbd16@mail.gmail.com>

Peter Harris wrote:

Show 23 quoted lines

> 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