Hi, I've been studying the codebase and looking for older emails in the ML that discussed what I want to propose as my GSoC project. In particular, I found a thread about slow git commands on chromium, so I reached them out at chromium's ML to ask if it's still an issue. I got the following answer: On Wed, Apr 3, 2019 at 1:41 PM Erik Chen <erikchen@xxxxxxxxxxxx> wrote: > Yes, this is absolutely still a problem for Chrome. I filed some bugs for common operations that are slow for Chrome: git blame [1], git stash [2], git status [3] > On Linux, blame is the only operation that is really problematic. On macOS and Windows ... it's hard to find a git operation that isn't slow. :( I don't really know if treading would help stash and status, but I think it could help blame. By the little I've read of blame's code so far, my guess is that the priority queue used for the commits could be an interface for a producer-consumer mechanism and that way, assign_blame's main loop could be done in parallel. And as we can se at [4], that is 90% of the command's time. Does this makes sense? But as Duy pointed out, if I recall correctly, for git blame to be parallel, pack access and diff code would have to be thread-safe first. And also, it seems, by what we've talked earlier, that this much wouldn't fit all together in a single GSoC. So, would it be a nice GSoC proposal to try "making code used by blame thread-safe", targeting a future parallelism on blame to be done after GSoC? And if so, could you please point me out which files should I be studying to write the planning for this proposal? (Unfortunately I wasn't able to study pack access and diff code yet. I got carried on looking for performance hostposts and now I'm a bit behind schedule :( Also, an implementation for fuzzy blame is being developer right now[5] and Jeff (CC-ed) suggested recently another performance improvement that could be done in blame[6]. So I would like to know wether you think it is worthy putting efforts trying to parallelize it. Thanks again for all the support. Matheus Tavares [1] https://bugs.chromium.org/p/git/issues/detail?id=18&q= [2] https://bugs.chromium.org/p/git/issues/detail?id=17&q= [3] https://bugs.chromium.org/p/git/issues/detail?id=16&q= [4] https://i.imgur.com/XmyJMuE.png [5] https://public-inbox.org/git/20190403160207.149174-1-brho@xxxxxxxxxx/T/#mb772910506e99e00337e4606f8377f95ef41c8c6 [6] https://public-inbox.org/git/87ftqz5osx.fsf@xxxxxxxxxxxxxxxxx/T/#m9caa63d35d39de8d2b7c5c6852f331dc2328e1ea
