Vault Server 3.06 under stress: where is the bottle neck?

Tri · Post by **Tri** » Mon May 02, 2005 7:32 pm

I have juste updated our server to 3.06. In the update procedure, I have recommended my fellows to delete the Vault client local cache. As a result, the server slows down significantly today as everybody updated their clients and renew the client cache.

Can you please advise:

- Where is likely the bottle neck when Vault server is under stress? SQL2K server or IIS server?

- What do you recommend to improve the server responsiveness when it is stressed under a sudden load?

Post by **jclausius** » Mon May 02, 2005 7:39 pm

Vault 3.0.7 should alleviate some of these problems.

Tri · Post by **Tri** » Tue May 03, 2005 1:39 pm

Just for my own curiosity. I'd like to know which is the slower part in Vault Server operations. Web Services or Communication with SQL Server?

Post by **jclausius** » Tue May 03, 2005 2:19 pm

The current design places most of the workload on SQL Server. After that, the second biggest constraint will be in transferring data to/from the client.

ismangil · Post by **ismangil** » Tue May 10, 2005 4:00 am

jclausius wrote:Vault 3.0.7 should alleviate some of these problems.

I read the release notes but wasn't clear whether "refresh" means get latest to an empty non working directory.

The situation is I am in the process of trialling continuous integration, we may several builds running concurrently, all doing "get latest version". I did notice the database server sustaining heavy CPU utilization.

Post by **jclausius** » Tue May 10, 2005 7:18 am

"Refresh" is the process in which the client updates its local cache information.

During a GET operation, the database's will be hit while the files in the GET request are retrieved from the database.

ismangil · Post by **ismangil** » Tue May 10, 2005 7:48 am

jclausius wrote:"Refresh" is the process in which the client updates its local cache information.

During a GET operation, the database's will be hit while the files in the GET request are retrieved from the database.

So would I get any performance enhancements using 3.0.7 compared with 3.0.6?

Post by **jclausius** » Tue May 10, 2005 8:01 am

Yes.

There were a couple of instances which are optimized for the refresh operation. In most cases, the performance of the IDE / GUI clients gets a small boost. All this is done by simply upgrading the Vault server.

Tri · Post by **Tri** » Mon May 16, 2005 2:00 pm

jclausius wrote:Yes.

There were a couple of instances which are optimized for the refresh operation. In most cases, the performance of the IDE / GUI clients gets a small boost. All this is done by simply upgrading the Vault server.

We have requested the developers to update Vault client to 3.06 two weeks ago. I don't feel like doing it again for 3.07 now. As the fix for 3.07 mainly addresses server improvement, is it OK to just update the server? (most of clients will be still 3.06)

Post by **jclausius** » Mon May 16, 2005 7:20 pm

Yes. Vault 3.0.7 addresses some immediate server issues that affect the Vault Server.

Leaving the client at Vault 3.0.6 will be fine.