Re: Git blame performance on files with a lot of history

On Fri, Dec 14, 2018 at 1:31 PM Derrick Stolee wrote: > > Please double-check that you have the 'core.commitGraph' config setting > enabled, or you will not read the commit-graph at run-time: > > git config core.commitGraph true > Yeah, this is what happens when trying too many things at onc

Re: Git blame performance on files with a lot of history

did hOn Fri, Dec 14, 2018 at 11:10 AM Bryan Turner wrote: > > After you converted the repository from CVS to Git, did you run a manual > repack? > > The process of converting a repository from another SCM often results > in poor delta chain selections which result in a repository that's > unneces

Re: Git blame performance on files with a lot of history

On Fri, Dec 14, 2018 at 2:48 PM Ævar Arnfjörð Bjarmason wrote: > > > On Fri, Dec 14 2018, Clement Moyroud wrote: > > > My group at work is migrating a CVS repo to Git. The biggest issue we > > face so far is the performance of git blame, especially compared to > >

Git blame performance on files with a lot of history

Hello, My group at work is migrating a CVS repo to Git. The biggest issue we face so far is the performance of git blame, especially compared to CVS on the same file. One file especially causes us trouble: it's a 30k lines file with 25 years of history in 3k+ commits. The complete repo has 200k+ c