# [GSoC][RFC] New approach: improve threading at git-grep

1 messages from 2019-06-10 to 2019-06-10. Participants: Matheus Tavares Bernardino.
Thread: https://gitlist.dev/t/51282

## Matheus Tavares Bernardino, 2019-06-10 16:47

Subject: [GSoC][RFC] New approach: improve threading at git-grep
Message-ID: <CAHd-oW5ifDZ_MmtmkuQt0FMpG74F=MZeUZ0yw7nq0xjOcwN-nA@mail.gmail.com>
URL: https://gitlist.dev/e/CAHd-oW5ifDZ_MmtmkuQt0FMpG74F%3DMZeUZ0yw7nq0xjOcwN-nA%40mail.gmail.com

```
Hi, everyone

I've been working on making the pack access code thread safe, as my
GSoC project[1]. I was working directly at sha1-file.c global states
targeting, in the far distance, to parallelize git-blame. But my
mentors and I decided to take a different path, as a better way to
continuous validate the work being done and be able to see small
continuous improvements: the idea is to focus on the object store call
chains originated at git-grep. Making them thread-safe, we should be
able to re-enable threading when greping blobs[2] and go refining
git-grep's locks along the way, for a better performance.

I just posted about the overall idea together with some analysis I've
made on git-grep, here:
https://matheustavares.gitlab.io/posts/week-4-a-different-approach
Please, let me know if you have any comments or suggestions.

Thanks,
Matheus

[1]: https://matheustavares.gitlab.io/assets/Matheus_Tavares_GSoC_Proposal.pdf
[2]: Disabled by 53b8d93 (“grep: disable threading in non-worktree
case”, 2011-12-12), because it was causing slowdowns

```
