{"thread":{"id":"19646","subject":"git and multiple cores","startedAt":"2009-06-02T22:40:12Z","lastAt":"2009-06-02T23:54:03Z","messageCount":6,"participants":["Chris Friesen","Peter Harris","Shawn O. Pearce","Nicolas Pitre"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"115287","messageId":"4A25AA4C.9070600@nortel.com","threadId":"19646","inReplyTo":null,"subject":"git and multiple cores","fromName":"Chris Friesen","fromEmail":"cfriesen@nortel.com","sentAt":"2009-06-02T22:40:12Z","receivedAt":"2009-06-02T22:40:12Z","isPatch":false,"sender":{"key":"cfriesen@nortel.com","avatar":null},"body":"\nI'm using git 1.6.1.3 and it seems to be limited to a single core.\nGiven that I've seen cases where the cpu has been basically pinned for\nminutes on end (initial clone of a repository, for instance) has there\nbeen any discussion of taking advantage of multiple cores?\n\nChris\n"},{"id":"115288","messageId":"eaa105840906021555w22e62341l61f250455cf8c23b@mail.gmail.com","threadId":"19646","inReplyTo":"4A25AA4C.9070600@nortel.com","subject":"Re: git and multiple cores","fromName":"Peter Harris","fromEmail":"git@peter.is-a-geek.org","sentAt":"2009-06-02T22:55:22Z","receivedAt":"2009-06-02T22:55:22Z","isPatch":false,"sender":{"key":"git@peter.is-a-geek.org","avatar":null},"body":"On Tue, Jun 2, 2009 at 6:40 PM, Chris Friesen wrote:\n>\n> I'm using git 1.6.1.3 and it seems to be limited to a single core.\n> Given that I've seen cases where the cpu has been basically pinned for\n> minutes on end (initial clone of a repository, for instance) has there\n> been any discussion of taking advantage of multiple cores?\n\nSounds like you're mostly concerned about packing.\n\nThe good news is, your version of git already has a threaded packer.\nYou just need to enable it. See \"pack.threads\" in \"git help config\".\n\n1.6.2 and newer use multiple threads by default.\n\nPeter Harris\n"},{"id":"115292","messageId":"20090602230205.GL30527@spearce.org","threadId":"19646","inReplyTo":"eaa105840906021555w22e62341l61f250455cf8c23b@mail.gmail.com","subject":"Re: git and multiple cores","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2009-06-02T23:02:05Z","receivedAt":"2009-06-02T23:02:05Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Peter Harris wrote:\n> On Tue, Jun 2, 2009 at 6:40 PM, Chris Friesen wrote:\n> >\n> > I'm using git 1.6.1.3 and it seems to be limited to a single core.\n> > Given that I've seen cases where the cpu has been basically pinned for\n> > minutes on end (initial clone of a repository, for instance) has there\n> > been any discussion of taking advantage of multiple cores?\n> \n> Sounds like you're mostly concerned about packing.\n> \n> The good news is, your version of git already has a threaded packer.\n> You just need to enable it. See \"pack.threads\" in \"git help config\".\n> \n> 1.6.2 and newer use multiple threads by default.\n\nTrue, but he was talking about initial clone, which on the client\nside is git-index-pack. Which is not threaded.\n \n-- \nShawn.\n"},{"id":"115293","messageId":"eaa105840906021612y5b9e4c25o1062d7f7aecfbd16@mail.gmail.com","threadId":"19646","inReplyTo":"20090602230205.GL30527@spearce.org","subject":"Re: git and multiple cores","fromName":"Peter Harris","fromEmail":"git@peter.is-a-geek.org","sentAt":"2009-06-02T23:12:11Z","receivedAt":"2009-06-02T23:12:11Z","isPatch":false,"sender":{"key":"git@peter.is-a-geek.org","avatar":null},"body":"On Tue, Jun 2, 2009 at 7:02 PM, Shawn O. Pearce wrote:\n> Peter Harris wrote:\n>> On Tue, Jun 2, 2009 at 6:40 PM, Chris Friesen wrote:\n>> >\n>> > I'm using git 1.6.1.3 and it seems to be limited to a single core.\n>> > Given that I've seen cases where the cpu has been basically pinned for\n>> > minutes on end (initial clone of a repository, for instance) has there\n>> > been any discussion of taking advantage of multiple cores?\n>>\n>> Sounds like you're mostly concerned about packing.\n>>\n>> The good news is, your version of git already has a threaded packer.\n>> You just need to enable it. See \"pack.threads\" in \"git help config\".\n>>\n>> 1.6.2 and newer use multiple threads by default.\n>\n> True, but he was talking about initial clone, which on the client\n> side is git-index-pack.  Which is not threaded.\n\nAh. I thought he was talking about the server side. My mistake.\n\nPeter Harris\n"},{"id":"115295","messageId":"4A25B5C3.40409@nortel.com","threadId":"19646","inReplyTo":"eaa105840906021612y5b9e4c25o1062d7f7aecfbd16@mail.gmail.com","subject":"Re: git and multiple cores","fromName":"Chris Friesen","fromEmail":"cfriesen@nortel.com","sentAt":"2009-06-02T23:29:07Z","receivedAt":"2009-06-02T23:29:07Z","isPatch":false,"sender":{"key":"cfriesen@nortel.com","avatar":null},"body":"Peter Harris wrote:\n> On Tue, Jun 2, 2009 at 7:02 PM, Shawn O. Pearce wrote:\n> \n>>Peter Harris wrote:\n>>\n>>>On Tue, Jun 2, 2009 at 6:40 PM, Chris Friesen wrote:\n>>>\n>>>>I'm using git 1.6.1.3 and it seems to be limited to a single core.\n>>>>Given that I've seen cases where the cpu has been basically pinned for\n>>>>minutes on end (initial clone of a repository, for instance) has there\n>>>>been any discussion of taking advantage of multiple cores?\n>>>\n>>>Sounds like you're mostly concerned about packing.\n>>>\n>>>The good news is, your version of git already has a threaded packer.\n>>>You just need to enable it. See \"pack.threads\" in \"git help config\".\n>>>\n>>>1.6.2 and newer use multiple threads by default.\n>>\n>>True, but he was talking about initial clone, which on the client\n>>side is git-index-pack. Which is not threaded.\n> \n> \n> Ah. I thought he was talking about the server side. My mistake.\n\nSorry, I wasn't clear. I was talking about the client side, although\nthe server side information is useful to have.\n\nI have a 4-way machine as a client, and it just seemed odd that git\ncould only use one core.\n\nChris\n"},{"id":"115296","messageId":"alpine.LFD.2.00.0906021949410.3906@xanadu.home","threadId":"19646","inReplyTo":"4A25B5C3.40409@nortel.com","subject":"Re: git and multiple cores","fromName":"Nicolas Pitre","fromEmail":"nico@cam.org","sentAt":"2009-06-02T23:54:03Z","receivedAt":"2009-06-02T23:54:03Z","isPatch":false,"sender":{"key":"nico@fluxnic.net","avatar":"https://avatars.githubusercontent.com/u/702790?v=4"},"body":"On Tue, 2 Jun 2009, Chris Friesen wrote:\n\n> Peter Harris wrote:\n> > On Tue, Jun 2, 2009 at 7:02 PM, Shawn O. Pearce wrote:\n> > \n> >>True, but he was talking about initial clone, which on the client\n> >>side is git-index-pack. Which is not threaded.\n> > \n> > \n> > Ah. I thought he was talking about the server side. My mistake.\n> \n> Sorry, I wasn't clear. I was talking about the client side, although\n> the server side information is useful to have.\n> \n> I have a 4-way machine as a client, and it just seemed odd that git\n> could only use one core.\n\nIt can use them all when repacking or pushing. But on a clone or fetch \nyour client machine deals with incoming data using index-pack which is \nmuch more trickier to thread.\n\n\nNicolas\n"}]}