Performance problems with Enhanced client in VS 2005/2008
Moderator: SourceGear
-
- Posts: 27
- Joined: Fri Jun 17, 2005 8:13 am
- Location: London, UK
Performance problems with Enhanced client in VS 2005/2008
We've just migrated from v3.5 to v4.1.1. We are now trying to use the enhanced client but we are having performance problems with the enhanced client in both VS 2005 and 2008.
It works but the IDE seems generally very slow, freezing from time time to time, especially comparing to the classic client. For instance, we have two branches of the same solution (gui app), one using the classic client and the other using enhanced client.
Opening them side by side in VS 2008, I can see a substantial difference in performance on very basic operations. Checking files in and out (exclusive) or getting the latest version are all slow using the enhanced client. After checking out a single file for instance in the enhanced client the IDE freezes for about 10 seconds. In the classic client on the other hand checking files out is instantaneous and the IDE is available without any noticeable delays.
Some of the users also reported IDE freezing on just saving files to the disk.
I enabled logging and have the log of checking out a single file using the enhanced client. After doing the simple things (actually checking out the file etc), it went on to do lots of other things like refreshing the whole solution tree by tree (the whole operation took ~17 seconds)! I can send you the log for you to have a look at.
It works but the IDE seems generally very slow, freezing from time time to time, especially comparing to the classic client. For instance, we have two branches of the same solution (gui app), one using the classic client and the other using enhanced client.
Opening them side by side in VS 2008, I can see a substantial difference in performance on very basic operations. Checking files in and out (exclusive) or getting the latest version are all slow using the enhanced client. After checking out a single file for instance in the enhanced client the IDE freezes for about 10 seconds. In the classic client on the other hand checking files out is instantaneous and the IDE is available without any noticeable delays.
Some of the users also reported IDE freezing on just saving files to the disk.
I enabled logging and have the log of checking out a single file using the enhanced client. After doing the simple things (actually checking out the file etc), it went on to do lots of other things like refreshing the whole solution tree by tree (the whole operation took ~17 seconds)! I can send you the log for you to have a look at.
Are these large projects?
If so, the next maintenance release should help with this. We made performance improvements in the Enhanced Client.
Vault 4.1.2 should be out in a day or two. We'd suggest that you upgrade, then if the slowdowns, persist, generate a new client log and send that to us along with the Vault Server log for the same time period.
The Vault server log is sgvault.log and is in %windir%\temp\sgvault on the server machine.
Send these as attachments to support at SourceGear.com Attn: Linda
If so, the next maintenance release should help with this. We made performance improvements in the Enhanced Client.
Vault 4.1.2 should be out in a day or two. We'd suggest that you upgrade, then if the slowdowns, persist, generate a new client log and send that to us along with the Vault Server log for the same time period.
The Vault server log is sgvault.log and is in %windir%\temp\sgvault on the server machine.
Send these as attachments to support at SourceGear.com Attn: Linda
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 27
- Joined: Fri Jun 17, 2005 8:13 am
- Location: London, UK
-
- Posts: 27
- Joined: Fri Jun 17, 2005 8:13 am
- Location: London, UK
Another issue with reverting to baseline
I've upgraded my local client to v4.1.2. The performance has indeed improved markedly (so far I've only had a look at in VS 2008. Will check out VS 2005 as well). It looks good.
However, I now have another problem. In VS 2008, I tried to check out a file, edit the source (ass a simple comment) and then tried to updo the check out. It seems to have worked: the file reverts back to displaying a padlock, VS no longer shows it as edited. But: the my edited text is still there! I have to physically close and re-open the file to get back to the baseline version.
Is this a known issue?
However, I now have another problem. In VS 2008, I tried to check out a file, edit the source (ass a simple comment) and then tried to updo the check out. It seems to have worked: the file reverts back to displaying a padlock, VS no longer shows it as edited. But: the my edited text is still there! I have to physically close and re-open the file to get back to the baseline version.
Is this a known issue?
-
- Posts: 27
- Joined: Fri Jun 17, 2005 8:13 am
- Location: London, UK
The solution has 9 projects (GUI app - several libraries, GUI front-end - windows forms, database project and a set up project).
I have tried it on a class file (vb.net). when I do an undo check out from the context menu, I can still see my changes. Clicking in the open editor window with the source, causes the VS to prompt me if I want to reload the file (it changed outside of the IDE, do you want to reload it?). If I say yes it does reload the file.
I also tried it on a windows form and the behaviour is different. Undoing the checkout from the context menu or the file in the project tree does the same: the file appears to have reverted but I can still see my changes in the editor. The IDE does not prompt me to reload it at all. The only way to do it is to close and re-open the form in IDE.
I tried saving the file on the disk after making changes and before undoing check out. It makes no difference.
I also tried to use the pending changes window. That seems to work OK - everything gets re-loaded properly.
[Edited]: Oh yes, it does appear to be a persistent problem.
I have tried it on a class file (vb.net). when I do an undo check out from the context menu, I can still see my changes. Clicking in the open editor window with the source, causes the VS to prompt me if I want to reload the file (it changed outside of the IDE, do you want to reload it?). If I say yes it does reload the file.
I also tried it on a windows form and the behaviour is different. Undoing the checkout from the context menu or the file in the project tree does the same: the file appears to have reverted but I can still see my changes in the editor. The IDE does not prompt me to reload it at all. The only way to do it is to close and re-open the form in IDE.
I tried saving the file on the disk after making changes and before undoing check out. It makes no difference.
I also tried to use the pending changes window. That seems to work OK - everything gets re-loaded properly.
[Edited]: Oh yes, it does appear to be a persistent problem.
-
- Posts: 27
- Joined: Fri Jun 17, 2005 8:13 am
- Location: London, UK
But the IDE does not prompt me to reload windows form files at all. It only does it on standard classes (as far as I can see).
It also does the same if I undo check out on the file in the project tree in the solution explorer. Only undoing checked out files via the pending changes window seems to work OK.
It also does the same if I undo check out on the file in the project tree in the solution explorer. Only undoing checked out files via the pending changes window seems to work OK.