views:

63

answers:

1

Have this currently problem with TorotiseGit - Show Log taking ages to populate with the history.

We have a repository with 300,000 files and recently about 3000 revisions ago, the administrator did a SVN move of one of the main directory's. Yes this means all 250,000 files where moved from one directory to the next.

The biggest problem is that GIT GUI can show a very fast Log of all the revisions and changes, and only when you click on it does it actually populate with whats changed. In TorotiseGit - Show Log, when it hits the revision it takes ages 30-40 minutes just to do one revision that included moving 250,000 files from one location to the next.

Is there any way, that you can tell TorotiseGit to Cache the Show Log results or a flag you can set so it does not do a deep search in what happened during that revision?

Thank you for any Answers.

+1  A: 

I cloned our SVN repository that contains 40-50 gigs of content and code. TortoiseGit just showed horrible logging performance, eg.. 15 minutes to bring up a log on a file. The inbuilt GIT GUI was fast, but did not allow the history of a single file, unless you searched for it.

I did not consider GIT extentions as an alternative, due to no SVN connectivity to our main SVN repository. Though GitExtentions did show better performance than TortoiseGit and would be the choice if we had our main repository as GIT instead of SVN.

In the end, TortoiseGit vs TortoiseSVN even though TortoiseSVN has to go over the network for its revision and check for modification was faster than TortoiseGit! So what does this mean? Well GIT works effectively but the GUI to git TortoiseGit sucks balls. Better of staying with SVN unless you manage less than 5 gigs of content then GIT with TortoiseGit will be a better solution.

Actually, I would recommend against GIT and just clone the damn SVN repository locally with VisualSVN server that is free. That way you get a clone of the SVN repository and its damn ** fast.

Chad