Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issue: this plugin is almost not useable with large project. #2347

Closed
flyingosprey opened this issue Oct 9, 2024 · 1 comment

Comments

@flyingosprey
Copy link

On large project which has 10k commits or more, "G log"/"Gclog"/"Gllog" is very slow, which is not usable. (too slow to use)

I think the reason is because above cmd try to pull all commit info in 1 time. On larget project, this 1 time action take very log time.

So can "G log"/"Gclog"/"Gllog" support pagenation? or support "load more"?

pagenation: this is how "git log" works. It loads commit info page by page.

"load more": This is how VSCode + gitlens plugin works. It queris a limit number of commit info. And there is a button "load more", which allows user to load more commit info if needed.

The most simple way to repro this issue: clone linux repro. Then run above 3 command. They ALMOST don't work because of the perf issue. The command takes very long time to finish.

Thanks.

[The request orignates from this questions https://github.com//discussions/2344. Please close one or both if making nonsense to you. ]

@tpope
Copy link
Owner

tpope commented Oct 9, 2024

I have no plans to add pagination at this time. I favor the simplicity of a :Git output being the exact output of the given command. Recommended workaround is :Git log -1000.

@tpope tpope closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants