Hello, using a 2.06 client and 2.06 server. When I start Vault client first thing in the morning (i.e. no one used it all night long), it takes a while to just display the list of repositories. Like 20-30 seconds.
On the server, the aspnet_wp process is going pretty crazy (according to the task manager anyway). I realize that there is start-up related slowdown, but 20-30 seconds to retrieve the list of repositories is pretty crazy.
Is there anything I can do on either client or server to speed up this process?
thanks.
Vault client takes a while to startup
Moderator: SourceGear
Does this happen anytime you close and open the Vault client or just in the morning?
If it happens just in the morning, it's possible that the aspnet_wp process was restarted or recycled during the night. If that's the case, the Vault server has to load everything into memory again. This could account for aspnet_wp "going crazy." Making sure you have enough in the way of hardware resources could help.
Also, if you are using the IDE client (integration with Visual Studio), this operation can be slow.
If it happens anytime you close and reopen the Vault client, then we should take a look at the sgvault.log file (%windir%\temp\sgvault) to see if there are any clues.
If it happens just in the morning, it's possible that the aspnet_wp process was restarted or recycled during the night. If that's the case, the Vault server has to load everything into memory again. This could account for aspnet_wp "going crazy." Making sure you have enough in the way of hardware resources could help.
Also, if you are using the IDE client (integration with Visual Studio), this operation can be slow.
If it happens anytime you close and reopen the Vault client, then we should take a look at the sgvault.log file (%windir%\temp\sgvault) to see if there are any clues.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Yep, first time around
Yes, mostly happens first time around. Is there anything I can do to prevent recycling from happening?
lbauer wrote:Does this happen anytime you close and open the Vault client or just in the morning?
If it happens just in the morning, it's possible that the aspnet_wp process was restarted or recycled during the night. If that's the case, the Vault server has to load everything into memory again. This could account for aspnet_wp "going crazy." Making sure you have enough in the way of hardware resources could help.
Also, if you are using the IDE client (integration with Visual Studio), this operation can be slow.
If it happens anytime you close and reopen the Vault client, then we should take a look at the sgvault.log file (%windir%\temp\sgvault) to see if there are any clues.
If Vault is on Windows 2003 Server, you can adjust settings per this KB article:
http://support.sourcegear.com/viewtopic.php?t=1014
Note: Vault 3.0.7 and 3.1 Beta optimize these settings for Vault during installation, so if you upgrade, you shouldn't have to make these manual adjustments.
http://support.sourcegear.com/viewtopic.php?t=1014
Note: Vault 3.0.7 and 3.1 Beta optimize these settings for Vault during installation, so if you upgrade, you shouldn't have to make these manual adjustments.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I am on Win2k (IIS 5). Is there anything for that?
lbauer wrote:If Vault is on Windows 2003 Server, you can adjust settings per this KB article:
http://support.sourcegear.com/viewtopic.php?t=1014
Note: Vault 3.0.7 and 3.1 Beta optimize these settings for Vault during installation, so if you upgrade, you shouldn't have to make these manual adjustments.