On Thu, Apr 04, 2019 at 09:56:35AM +0200, Christian Couder wrote: > Hi, > > On Thu, Apr 4, 2019 at 3:15 AM Matheus Tavares Bernardino > <matheus.bernardino@xxxxxx> wrote: > > > > 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. :( > > Nice investigation. About git status I wonder though if they have > tried the possible optimizations, like untracked cache or > core.fsmonitor. Note that one known issue on macOS specifically on large repos is that the number of files explodes the inode cache in the kernel, and lstat becomes slow. e.g. https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/p9U4jqz8kxo Mike
