Slow Commits/Reflog tab #2396
Unanswered
gprocopciucnxp
asked this question in
Q&A
Replies: 2 comments 1 reply
-
This is also slow on the kernel git repository. I dig into code of git and it seems that if --xxx-order is set, the limit we set to git log doesn't make git parse less commit history. I have a perf on the command above, and I found that git spends most time in decompress data. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I found a perfect solution:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
First of all, I would like to say a big thank you to all contributors to this project! It's really helpful and makes the interaction with git much easier and, quicker.
I updated the lazygit to the latest released version and observed a significant slowdown of the Commits/Reflog tab during startup. It takes ~15 seconds to be populated for the Linux Kernel project. Here are the steps to be reproduced:
git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
test@workstation:~$ lazygit --version commit=d1a8b05401ccda1e52215203139a252eb3be3b79, build date=2022-11-14T09:22:31Z, build source=binaryRelease, version=0.36.0, os=linux, arch=amd64, git version=2.32.0
Observed behavior:
It takes ~15 seconds to load the 'Reflog/Commits' view, which is a lot of time.
I took a look into strace output. This takes most of the above-mentioned startup time:
The
--topo-order
parameter seems to be the source of the slowdown. I have tried some other commit ordering rules, but with no success; all of them are slow.Only the removal or usage of the default order helped in my case. This is my dirty patch which I suppose has to be transformed into a new option. E.g
git.log.order: 'default'
Regards,
Ghennadi
Beta Was this translation helpful? Give feedback.
All reactions