* git and multiple cores
@ 2009-06-02 22:40 Chris Friesen
2009-06-02 22:55 ` Peter Harris
0 siblings, 1 reply; 6+ messages in thread
From: Chris Friesen @ 2009-06-02 22:40 UTC (permalink / raw)
To: git
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?
Chris
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git and multiple cores
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
0 siblings, 1 reply; 6+ messages in thread
From: Peter Harris @ 2009-06-02 22:55 UTC (permalink / raw)
To: Chris Friesen; +Cc: git
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.
Peter Harris
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git and multiple cores
2009-06-02 22:55 ` Peter Harris
@ 2009-06-02 23:02 ` Shawn O. Pearce
2009-06-02 23:12 ` Peter Harris
0 siblings, 1 reply; 6+ messages in thread
From: Shawn O. Pearce @ 2009-06-02 23:02 UTC (permalink / raw)
To: Peter Harris; +Cc: Chris Friesen, git
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.
--
Shawn.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git and multiple cores
2009-06-02 23:02 ` Shawn O. Pearce
@ 2009-06-02 23:12 ` Peter Harris
2009-06-02 23:29 ` Chris Friesen
0 siblings, 1 reply; 6+ messages in thread
From: Peter Harris @ 2009-06-02 23:12 UTC (permalink / raw)
To: Shawn O. Pearce; +Cc: Chris Friesen, git
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.
Peter Harris
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git and multiple cores
2009-06-02 23:12 ` Peter Harris
@ 2009-06-02 23:29 ` Chris Friesen
2009-06-02 23:54 ` Nicolas Pitre
0 siblings, 1 reply; 6+ messages in thread
From: Chris Friesen @ 2009-06-02 23:29 UTC (permalink / raw)
To: Peter Harris; +Cc: Shawn O. Pearce, git
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git and multiple cores
2009-06-02 23:29 ` Chris Friesen
@ 2009-06-02 23:54 ` Nicolas Pitre
0 siblings, 0 replies; 6+ messages in thread
From: Nicolas Pitre @ 2009-06-02 23:54 UTC (permalink / raw)
To: Chris Friesen; +Cc: Peter Harris, Shawn O. Pearce, git
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-06-02 23:54 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox