git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git and multiple cores

From
Nicolas Pitre <nico@cam.org>
Date
Jun 2, 2009, 23:54 UTC
Message-ID
<alpine.LFD.2.00.0906021949410.3906@xanadu.home>
In-Reply-To
<4A25B5C3.40409@nortel.com>
On Tue, 2 Jun 2009, Chris Friesen wrote:
Show 14 quoted lines
> 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
Previous: Chris Friesen
Message 6 of 6 in “git and multiple cores”
  1. Chris FriesenJun 2, 2009
  2. Peter HarrisJun 2, 2009
  3. Shawn O. PearceJun 2, 2009
  4. Peter HarrisJun 2, 2009
  5. Chris FriesenJun 2, 2009
  6. Nicolas PitreJun 2, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.