Does CCNet server affect the performance of SourceGear Vault

[sneh]

1]I want to know if integrating CCnet server with SourceGear Vault affects the performance of Vault.

If yes, is it advisable to limit the integration process to 2-3 times a day as opposed to integration process on every modification.

2]Also, I would like to know what are other factors affecting the performance of sourcegear vault. (eg: old histories, too many project on the vault server)

Thanks

[ismangil]

1]I want to know if integrating CCnet server with SourceGear Vault affects the performance of Vault.

If yes, is it advisable to limit the integration process to 2-3 times a day as opposed to integration process on every modification.

2]Also, I would like to know what are other factors affecting the performance of sourcegear vault. (eg: old histories, too many project on the vault server)

Thanks

[1] I believe the answer is yes, judging from the latest 3.1.7 release notes where they said there were specific improvements relating to CCNet interaction with Vault.

[ian_sg]

In the latest version of Vault, performance implications for a typical (or what I'm going to guess is typical) CC.NET install are minimal. Of course, if you've got dozens of projects set to look for changes every 30 seconds, there's going to be some impact. There are a lot of variables here: network latency, number of developers using Vault, number of CC.NET projects, etc. So there's is no definitive and simple answer. At SourceGear we're running 12 projects, all checking for changes in 3 different repositories every 2 minutes, on servers that are several years old, and haven't had any performance issues.

As far as your other performance-related question, I'll direct you here: Recommendations for optimal Vault performance.