LazyGit is unusably slow in big repos like nixpkgs

[valyntyler]

Seems similar to #2875, though I am not familiar enough to say.
Recently became interested in contributing to nixpkgs which is probably the hugest repository ever ever, and gets like a garrilion PRs merged every femtosecond. Because of that, LazyGit seems to have a very unfun time trying to load it. It takes multiple dozen seconds to even open the app and any git operations would be done faster on a turing machine. Curiously CLI commands like git log seem to do fine despite the history of the repo being epically long. This is probably because git log does not attempt to load the entire history of the project, but again, I'm too smooth brain to know these things.
Would appreciate any insight on this, and I thank you for the precious seconds spent reading this, that you're never ever getting back btw

[stefanhaller]

Seems similar to #2875, though I am not familiar enough to say.

Yes, and the recommendation there helps here, too. On my machine it takes 8s until lazygit shows the commits list; if I add

git:
  log:
    order: default

it becomes instantaneous. Note that you should add this to a local config file (nixpkgs/.git/lazygit.yml), because in smaller repos you want lazygit's default of topo-order.

Also note that this doesn't solve all problems; for example, typing / to search in the commits list makes it hang for me (I killed it after a few minutes). This is because at that point it tries to load all commits rather than just the first 300, and that takes forever.

Improving this would require fundamental architectural changes that are currently not on my roadmap, so for now you'll have to avoid those operations that make it hang on such a large repo.