Re: Questions on GSoC 2019 Ideas
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Mar 5, 2019, 12:57 UTC
- Message-ID
- <CACsJy8D-eQUGFsu4_cB9FE6gAo2d68EF_x2ze3YLXKAxYJfhSQ@mail.gmail.com>
- In-Reply-To
- <20190305045140.GH19800@sigill.intra.peff.net>
On Tue, Mar 5, 2019 at 11:51 AM Jeff King <peff@peff.net> wrote:
Show 13 quoted lines
> > processing power from multiple cores, but about _not_ blocking. I > > think one example use case here is parallel checkout. While one thread > > is blocked by pack access code for whatever reason, the others can > > still continue doing other stuff (e.g. write the checked out file to > > disk) or even access the pack again to check more things out. > > I'm not sure if it would help much for packs, because they're organized > to have pretty good cold-cache read-ahead behavior. But who knows until > we measure it. > > I do suspect that inflating (and delta reconstruction) done in parallel > could be a win for git-grep, especially if you have a really simple > regex that is quick to search.
Maybe git-blame too. But this is based purely on me watching CPU utilization of one command with hot cache. For git-blame though, diff code as to be thread safe too but that's another story.
-- Duy