There are a couple of possible reasons which may result in slower refreshing:

Be sure that you have no local nor staged changes, before doing so!

If you encounter wrong .git/index timestamps frequently, please contact [email protected]

If an invocation of git status is rather slow, too, you may also want to try the following:

If many of your ignored files are located directly in the out/-directory, following .gitignore line will be efficient:


while this line will be inefficient:


Furthermore, if there is just a single tracked file located in out/ or one of its subdirectories, the ignore-processing will be inefficient.

Many Refs

Large amounts of tags (or branches) may slow down Logs, but also the Working Tree window. You can tell SmartGit to exclude certain tags or remote branches from loading by using Java regular expressions with following options in .git/config:

[smartgit "refLimit"]
    tagIncludeRegEx = smart.*
tagExcludeRegEx = .*-I\\d{8}-\\d{4}
remoteBranchIncludeRegEx =
remoteBranchExcludeRegEx =

If an include regular expression matches the tag/remote branch name, it will be included, no matter whether the excluding pattern matches.

It is recommended to invoke a git pack-refs --all after doing so, to have the changes take effect in SmartGit.

Background operations

Depending on your connection to the server, background commands (especially the remote background commands), may take quite a long time and it can be helpful to turn them off in the Preferences, section Background Commands.

If you see SmartGit taking a long time for Updating remote state (in the status bar) after invoking commands like PushPull or Sync, this may be caused by unusual long execution times of git ls-remote refs/for/<branch>: check the log files to find the corresponding ls-remote invocation logging and see how long it takes. If it's actually the culprit, you may disable these remote state updates (per-remote) by adding following line to the appropriate [remote] section:

[remote ...]
  smartgitBackgroundFetch = false

Log Window

In addition to the above mentioned problems: