Slow Check in
Moderator: SourceGear
-
- Posts: 4
- Joined: Tue Jan 09, 2007 11:12 am
- Contact:
Slow Check in
We just moved several of our Sourcesafe databases on a new system and are facing unusual slowdown while checking in files from withing the SoS Client GUI (up to 2 mn for a simple 200 KB text file).
SoS Server is the standard 4.2 version running on a Win 2003 Std R2 Server with 2 cpu * 2 cores and 2 GB or memory.
The sourcesafe engine is in version 2005.
The client is also a 4.2 standard version.
Any help would be greatly appreciated.
SG
SoS Server is the standard 4.2 version running on a Win 2003 Std R2 Server with 2 cpu * 2 cores and 2 GB or memory.
The sourcesafe engine is in version 2005.
The client is also a 4.2 standard version.
Any help would be greatly appreciated.
SG
-
- Posts: 4
- Joined: Tue Jan 09, 2007 11:12 am
- Contact:
We still have our old server running with SoS 3.5.3 + VSS 6.0d. It supports our main development and the "check in" response time seems normal.
Both servers(new and old) are located in the same computer room, on the same LAN. Could you precise which details you are interested in?
PLease note that the problem also occurs with a local connection (Both server and client on the same LAN subnet).
Thanks for your concern.
SG
Both servers(new and old) are located in the same computer room, on the same LAN. Could you precise which details you are interested in?
PLease note that the problem also occurs with a local connection (Both server and client on the same LAN subnet).
Thanks for your concern.
SG
I think I see one issue right off the bat. You don't want a mismatch between the client and server. 3.5.3 clients should connect only to 3.5.3 servers and 4.2 clients should connect to 4.2 servers. If a client needs to use both, both SOS clients can be installed on the same machine, but I would suggest just changing the default install location.
Are both servers experiencing the slow-down?
Are all clients at 4.2 or is it mixed?
Are both servers experiencing the slow-down?
Are all clients at 4.2 or is it mixed?
-
- Posts: 4
- Joined: Tue Jan 09, 2007 11:12 am
- Contact:
I believe we did the installation in the right way.
I installed two clients on my computer and, for test purpose, use the 3.5.3 client only with the legacy 3.5.3 server and the 4.2 client with the 4.2 server. The clients are installed in separate folders ("SourceOffSite" for the 3.5.3 client and "SourceOffSite 4.2" for the 4.2 client).
The 3.5.3 client / server works fine.
SG
I installed two clients on my computer and, for test purpose, use the 3.5.3 client only with the legacy 3.5.3 server and the 4.2 client with the 4.2 server. The clients are installed in separate folders ("SourceOffSite" for the 3.5.3 client and "SourceOffSite 4.2" for the 4.2 client).
The 3.5.3 client / server works fine.
SG
-
- Posts: 4
- Joined: Tue Jan 09, 2007 11:12 am
- Contact:
Same behaviour with VSS 6.0d
Last update:
I had to come back to VSS 6.0d for some other reasons.
I also reinstalled the SoS 4.2 server and client from scratch.
Before this I also removed the SoS 3.5.3 client.
I still have the same 2 mn delay when I check files in.
SG
I had to come back to VSS 6.0d for some other reasons.
I also reinstalled the SoS 4.2 server and client from scratch.
Before this I also removed the SoS 3.5.3 client.
I still have the same 2 mn delay when I check files in.
SG
Could you set the SOS Server to Debug and Method Logging perform a few actions where the slow down occurs and send me the log? Just send it to support at sourcegear.com (attn: Beth) and reference this post.