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

Re: git and multiple cores

From
PHPeter Harris <git@peter.is-a-geek.org>
Date
Jun 2, 2009, 22:55 UTC
Message-ID
<eaa105840906021555w22e62341l61f250455cf8c23b@mail.gmail.com>
In-Reply-To
<4A25AA4C.9070600@nortel.com>
On Tue, Jun 2, 2009 at 6:40 PM, Chris Friesen wrote:
Show 5 quoted lines
>
> 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
Previous: Chris FriesenNext: Shawn O. Pearce
Message 2 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.