Very Slow Performance after upgrade

Eiremon · Post by **Eiremon** » Fri Apr 14, 2006 8:02 am

We are running SOS 4.1.2, Server and Client...

We just upgraded our server to VSS 2005. We also performed an Analysis on the source database for the first time in a long time. Since then we have seen very poor performance in the SOS Server.

When we launch the SOS client from any machine and make a request to view the files in a project folder, the CPU utilization for SOS Server jumps to ~ 25% and stays in that range for over 10 seconds before responding with the file list. The client hangs on "Updating file list: ...." for about 10 seconds before getting the list ("Received file list:....").

Getting latest on a project tree is also taking a significant amount of time. We have tried restarting the SOS Server but that did not help. The server logs do not indicate any problems either.

lbauer · Post by **lbauer** » Fri Apr 14, 2006 8:14 am

When we tested SOS with VSS 2005, we made sure all the operations worked properly. We haven't done performance testing yet to compare using SOS with the different automation component versions, so it's possible that performance could be different with VSS 2005.

But let's rule out other possibilities first:

Is the VSS 2005 client installed on the SOS Server machine? Or are you using a different version of VSS there?

If you are using the VSS 2005 client, what version of VSS Client was previously installed on the SOS Server machine?

Has anything else changed on the SOS Server machine -- like the addition of anti-virus software, other applications using system resources, etc?

Eiremon · Post by **Eiremon** » Fri Apr 14, 2006 9:00 am

The VSS 2005 client is installed on the Server machine as well. The previous version was 6.0d.

I did disable virus scanning on the server recently, I would think that should improve performace. No new software has been installed.

4/14/2006 10:20:02 AM - SSAPI.dll Information:
4/14/2006 10:20:02 AM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
4/14/2006 10:20:02 AM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null

lbauer · Post by **lbauer** » Fri Apr 14, 2006 9:46 am

Code: Select all

4/14/2006 10:20:02 AM - SSAPI.dll Information: 
4/14/2006 10:20:02 AM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL 
4/14/2006 10:20:02 AM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null

Actually, this information comes from SOS and is the same in the log no matter what version of SourceSafe you're using. To determine which version of the SourceSafe automation component is installed on the SOS Server machine, see this KB article.
http://support.sourcegear.com/viewtopic.php?p=5293

Eiremon · Post by **Eiremon** » Fri Apr 14, 2006 12:01 pm

ssapi version is 8.0.50727.42.... We don't really need the client on the server, I will try using the old dll from 6.0d.

Eiremon · Post by **Eiremon** » Fri Apr 14, 2006 12:31 pm

In searching through some of the other posts I saw something related to the ThreadingModel of the VSS Automation component. I have switched this setting from "Apartment" to "Both". It looks like this may have fixed the problem...

rafa · Post by **rafa** » Tue May 20, 2008 11:28 am

Hi,

I have the same problem: The client hangs on "Updating file list". However, I am using VSS 6.0c (with hotfix) and SOS 4.2.

HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32 is not present in the registry. --> ThreadingModel is set to Both

What is wrong?

Thank you in advance.

rafa · Post by **rafa** » Tue May 20, 2008 11:46 am

Sorry "HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32" is present in the registry and ThreadingModel is set to Both but the problem persists.

lbauer · Post by **lbauer** » Tue May 20, 2008 3:39 pm

This could be network or database related.

When does the client hang? After login or after clicking on particular project?

Is this happening for all users on any machine, or just certain users?

Try connecting to the SOS Server using an SOS Client on the SOS Server machine, and use "localhost" for the SOS Server name. Does that hang as well?

We'd like to see a copy of the SOS log. Reproduce the problem and send a copy of the log file to support at sourcegear.com, Attn:Linda.

The SOS Server log is called log.txt and is in the SOS Server directory on the SOS Server machine.