4
One of my colleagues uses a Windows 7 machine with TortoiseGit and it is tortuously slow even just running a git status. He is using the TortoisePlink method of connection and key serving.
Each commit is taking about 5 minutes before the changed files list is populated let alone the actual commit itself. Pushing and pull take even more time and woe betide him when there is a merge conflict!
I am unsure what is causing it to be so slow as all operations appear to be compromised not just those that access the network (push/pull/etc).
The one caveat to all of this is that he is operating on files that are shared over Samba from an Ubuntu 10.10 box.
I have not had any luck getting it to run any faster on his machine by removing and re-installing TortoiseGit and MSysGit. Any other ideas to make it faster?
He is using TortoisePlink to be able to make use of Pageant and multiple keys.
Treffynnon
Posted 2011-03-15T09:57:38.677
Reputation: 269
1
He has cloned onto a Samba share on the server and not on his local machine. The reason for this is we have a central development server for our web applications with each developer having their own sub domain. Which I have documented http://blog.simonholywell.com/post/1516566788/team-development-server for anyone interested.
– Treffynnon – 2011-03-15T10:17:17.933A quick experiment cloning locally and cloning onto Samba shows markedly different results like you suggest. I am using Ubuntu and I work over the same Samba shares as well in the same way. My operations using git-cli over Samba is much faster and almost identical to the same operation performed on the server itself over SSH. – Treffynnon – 2011-03-15T10:20:18.480
I don't have time to read the article right now (and I know next to nothing about Apache), but are the developers RDP'ing or SSH'ing into the server and working there (if so, they should clone onto a local drive on the server), or are they developing locally and deploying onto the server (if so, they should clone first onto the dev server and then from the dev server onto a local drive on their own machines, and push changes to their dev server repo)? – Aasmund Eldhuset – 2011-03-15T10:57:08.077
I get what you mean. This particular developer does not have linux command line skills and works with HTML/CSS. So he works directly on the development server editing files via the samba share so he can see his changes in the web browser immediately. The git workflow you mention sounds good, but is a but cumbersome in practice given the type of work we do. It seems like I might have to look at the way his computer is working on the network. – Treffynnon – 2011-03-15T14:44:53.657
Thanks for your help though and we are going to give GitExtensions a go at the end of the working day. – Treffynnon – 2011-03-15T14:45:38.413