Slowness when right-clicking a project
Moderator: SourceGear
Slowness when right-clicking a project
In the Solution Explorer, when I right-click on a Project that contains a lot of .sql files, there is something like a 10-second delay before the context menu displays. This delay is not present when I simply select the project.
Is Vault doing some kind of sweep on everything in the project whenever I right-click it? This is causing a problem. We use this project to store all of our .sql files for database stored procedures etc. Having this kind of delay every time I try to right-click on one of the upper-level folders to add a new item is a serious slow down.
Is Vault doing some kind of sweep on everything in the project whenever I right-click it? This is causing a problem. We use this project to store all of our .sql files for database stored procedures etc. Having this kind of delay every time I try to right-click on one of the upper-level folders to add a new item is a serious slow down.
Are you performing this right-click in Visual Studio? If so, which version of VS?
I don't currently have an reports of a slow down on just certain types of files, so we'll have to do a little more digging to see if this is due to the file type or something else.
Can you open a Vault GUI and go to Help - Technical Support and post the complete environment information from there?
I don't currently have an reports of a slow down on just certain types of files, so we'll have to do a little more digging to see if this is due to the file type or something else.
Can you open a Vault GUI and go to Help - Technical Support and post the complete environment information from there?
Client Information
Vault Client Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)
Server Information
Vault Server Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
1 serial number(s):
1 of 1: 5 full users, permanent
Vault Client Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)
Server Information
Vault Server Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
1 serial number(s):
1 of 1: 5 full users, permanent
One thing that may help is install the latest .NET service packs on your server. I've run into a few strange things happening due to both mis-matching .NET versions and not having the latest service packs on though.
Another thing you can try would be to review our Recommendations for optimal Vault performance. The recommendations there usually help a lot. Once you've tried those out, let me know if it's still slow.
Another thing you can try would be to review our Recommendations for optimal Vault performance. The recommendations there usually help a lot. Once you've tried those out, let me know if it's still slow.
-
- Posts: 5
- Joined: Mon Sep 03, 2007 10:35 am
felinesoft: When comparing VSIP to MCSCCI, I think MCSCCI might be faster on websites. The solution there would be to use the MCSCCI interface instead. We do have this logged as a bug and developers are working on it, but I don't know when it will be fixed. If you check the release notes before downloading a version, you'll be able to see what fixes were in that release, or just check back with me later for an update. You can always email at support at sourcegear.com to check up on this.