vendorpolt.blogg.se - Sourcetree git flow slow

SOURCETREE GIT FLOW SLOW WINDOWS 10
SOURCETREE GIT FLOW SLOW WINDOWS 7
SOURCETREE GIT FLOW SLOW FREE
SOURCETREE GIT FLOW SLOW WINDOWS

Few of my teammates have the same problem, also on Windows 10.

SOURCETREE GIT FLOW SLOW WINDOWS 10

I haven't tried the latest Sourcetree on Windows 7, but I believe this is a Windows 10 related problem.

SOURCETREE GIT FLOW SLOW WINDOWS 7

Until few months ago I have been using Sourcetree also on a Windows 7 machine and the slowness problem didn't occur there. The test was done few days ago, on with the latest version of sourcetree. I'm running the latest Windows 10 (64-bit) with the latest updates. In fact, in the repos I have tested there were no untracked files. In the list of files, the view I'm using is "Flat list (single column)", and the filter is "Pending files, sorted by path" "git status" works OK on all of the repos. None of the files in the repos were opened in an editor while I was doing the test.

I have around 20 - 30 repositories bookmarked, but they were not open while I was doing this test.

SOURCETREE GIT FLOW SLOW FREE

The repos are located on the local hard disk (SSD), and there's more than enought free disk space on it >20GB.Īt the time of test I had 6 repositories opened. I have repeated the test with only two repos open which have a low number of commits (one has 2 commits, the other has 10) and no untracked files.Īll of my repos are on git (bitbucket) and I'm using the latest version of Git: After that further changing of tabs didn't increase the disk usage, but were still very slow.ĭuring the test the options "Refresh automatically when files change" and "Check default remotes for updated every 10 minutes" were both unchecked. The disk usage was most of the time on 0-1%, and it increased to 90% when I first changed a repo tab in Sourcetree. I have tried all of the actions above and all of them were slow.ĭuring this test, I have watched the system status in task manager, and everything was normal, there was no increase in CPU and memory usage. During this test I have shut down all other applications and antiviruses, and resident programs and services that I could shut down. Check default remotes for updated every 10 minutesīut it didn't help, the slowness remained.Refresh automatically when files change.

I have tried to uncheck this options in Tools -> Options:

probably some other actions that I missed to mentionĮach of this actions takes a long time (1-2 min) and meanwhile Sourcetree becomes unresponsive.įrom time to time (but very rare) some of this actions work without any slowness.

sometimes it just becomes unresponsive without me taking any action.

clicking the commit message box so that I can write a commit message.

changing to another repo tab and switching back to the first one.

opening sourcetree - it takes around 2 minutes.

Here are some of the actions that are very slow: The machines I'm working on are powerfull enough to run very demanding applications (i7 processor, 16GB RAM, Samsung Evo SSD disk). I have tried it on two different machines both using Windows 10, and it's extremely slow on both of them. With each new version it became more slower and slower, and in the latest version is extremely slow and totally unusable. Which will help you to visualize the git operations that are taking place.I have been using Sourcetree on Windows 10 for several months now, and since I started using it it was mouch slower than on Windows 7. If you are still unsure, you might want to use something like the following: If you look at the history of your git repository before and after the rebase operation, you should hopefully get a feel for what is happening. Replay commits from myfeature branch onto the head of the current develop branch So, looking at the "normal" finishing of a feature workflow from above, you would do something like the following: $ git checkout myfeature I would encourage you to try the following in isolation to get used to what is happening. NOTE: While a rebase operation is a perfectly normal workflow to follow, I use it almost daily, it can cause problems if you are just using it for the first time, especially if there are conflicts between the feature branch you are working on and what is on the develop branch. If you are not familiar with the git rebase operation, I would suggest that you read about it here first: The checkbox option in SourceTree likely does one additional step which is rebasing the current feature branch onto the head of the develop branch before merging. The original command line suggestions, which most GitFlow tooling is derived from can be found on the original blog post article here:Ĭlosing a feature branch consists of the following steps: $ git checkout develop