We're always on a quest to streamline the git experience as well as improve the performance of GitKraken Client. If you're experiencing slow performance, it can often be remedied using one of the troubleshooting steps below.
Perfomance issues in GitKraken Client are often related to a specific repository. Some large or complex repositories with many references may cause GitKraken Client to slow down.
How to troubleshoot slow performance
Perform a git gc on the repository.
Take a fresh clone of the repository to a new local directory.
Additional troubleshooting steps
Disable auto-fetch by setting the Auto-fetch Interval to 0.
Perform a git status on the repository.
Delete local branches that are not needed.
Soloing or Hiding branches/tags.
Make sure that GitKraken Client is set to only show the most recent 2,000 commits.
If working with an LFS repository, you can perfom an LFS prune.
If you are working on MacOS Big Sur, follow the directions in this article to address issues resulting from application signatures.
Restart GitKraken Client daily
Big Sur slowness
A change that came with macOS Big Sur has caused slowdowns in many applications. However, there is a workaround. Open your terminal and run the following:
codesign --remove-signature /Applications/GitKraken.app/Contents/Frameworks/GitKraken\ Helper\ \(Renderer\).app
This will remove the GitKraken Signature, making it a partially-signed app.
Note: This command will need to be ran each time you update GitKraken Client