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

Re: [git wiki PATCH 1/3] "Improving parallelism in various commands" project

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Mar 2, 2012, 14:29 UTC
Message-ID
<CACsJy8APtrw-6umkr3=yrG3wfye96=z=CvfWj0tnghfDcDWFzg@mail.gmail.com>
In-Reply-To
<57e8b4eb7a98af33982c2f3a763e18f62b1d6d6d.1330686331.git.trast@student.ethz.ch>
On Fri, Mar 2, 2012 at 6:05 PM, Thomas Rast <trast@student.ethz.ch> wrote:
> + * In preparation (the half-step): identify commands that could
> +   benefit from parallelism.  `git grep --cached` and `git grep
> +   COMMIT` come to mind, but most likely also `git diff` and `git log
> +   -p`.  You can probably find more.

I just had a thought this afternoon whether "git add" may benefit from parallelism. It's most likely I/O-bound, although I think if we add a bunch of large files, it might become CPU-bound. To generalize, anything that calls hash_sha1_file() might benefit from parallelism.

Another candidate may be git-apply. Actually I just want to speed up git-rebase and think git-apply may be the culprit. Or it could be unpack-trees code..

-- 
Duy
Previous: Thomas RastNext: James Pickens
Message 7 of 8 in “"Improving parallelism in various commands" project”
  1. 1/3 "Improving parallelism in various commands" projectThomas Rast, Mar 2, 2012
  2. 2/3 "Designing a faster index format" projectThomas Rast, Mar 2, 2012
  3. Jeff KingMar 2, 2012
  4. Junio C HamanoMar 2, 2012
  5. Nguyen Thai Ngoc DuyMar 3, 2012
  6. 3/3 "Improving the `git add -p` interface" projectThomas Rast, Mar 2, 2012
  7. Nguyen Thai Ngoc DuyMar 2, 2012
  8. James PickensMar 2, 2012

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.