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

Compute git statuses using the bundled git executable, not libgit2 #12444

Merged
merged 2 commits into from
May 29, 2024

Conversation

maxbrunsfeld
Copy link
Collaborator

I realized that somehow, the git executable is able to compute git status much more quickly than libgit2, so I've switched our git status logic to use git. Follow-up to #12266.

Release Notes:

  • Improved the performance of git status updated when working in large git repositories.

@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label May 29, 2024
@maxbrunsfeld maxbrunsfeld merged commit dd328ef into main May 29, 2024
8 checks passed
@maxbrunsfeld maxbrunsfeld deleted the dugite-status branch May 29, 2024 21:31
@izuzak
Copy link
Contributor

izuzak commented May 30, 2024

the git executable is able to compute git status much more quickly than libgit2

@maxbrunsfeld Just curious -- what was the difference in speed, do you remember some examples? And many thanks for making further improvements here -- Zed's speed was one of the main reasons why I started using it ❤️

maxbrunsfeld added a commit that referenced this pull request May 31, 2024
The quest for responsiveness in large git repos continues. This is a
follow-up to #12444

Release Notes:

- N/A
@shenjackyuanjie
Copy link
Contributor

shenjackyuanjie commented Jun 1, 2024

I'm looking forward to see GitoxideLabs/gitoxide#1264 works on zed :)
( 10 git.exe process a sec really looks scary

recording

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed The user has signed the Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants