Shadow Folder Latency

JonShrout · Post by **JonShrout** » Tue May 23, 2006 2:38 pm

I've noticed some (albeit minor) latency with shadow folder propagation.

I was wondering if there are any statistics available and/or if there is any way to optimize the propagation of changes to the shadow folder?

TIA,

Jon

lbauer · Post by **lbauer** » Tue May 23, 2006 3:49 pm

There's no way to change the Shadow Folder update time -- latency of a minute or two is not unusual. Are you experiencing something longer?

JonShrout · Post by **JonShrout** » Tue May 23, 2006 3:54 pm

..latency of a minute or two is not unusual. Are you experiencing something longer?

No, just wondering if there's a way to speed it up.

Thanks!

Jon

JonShrout · Post by **JonShrout** » Fri Jun 02, 2006 4:13 pm

We are using the [3.1.8] Vault Command Line Client for most source control operations. We also have a shadow folder setup for the repository.

I had a thought that I could 'speed up' the shadow folder update time by doing a 'Get Latest Version' operation to the shadow folder immediately after a file is checked in.

Are there any issues I should consider in doing this? Would this cause any problems?

TIA

lbauer · Post by **lbauer** » Sat Jun 03, 2006 4:00 pm

Using both the Shadow Folder Service and the CLC to update files in the same folder can cause problems. I'd suggest using one or the other, but not both.

The Shadow Folder Service is like a Vault Client in that it creates a cache file and keeps track of baselines. To update files, it only retrieves the "delta," not the entire file.

If you update the contents of the Shadow Folder with a "get" using the Command Line Client, the Shadow Folder Cache will be out of sync and files might not get updated properly.

JonShrout · Post by **JonShrout** » Mon Jun 05, 2006 1:32 pm

Vault 3.1.8 on Server 2003 Standard and clients on XP Pro

SQL Server 2005 on Server 2003 Standard

Vault DB and web services on same machine (I know) with Shadow Folder on different machine (Server 2003 Standard)

We've been experiencing Shadow Folder latency of 5-10 minutes. Any idea why this might be happening?

TIA

JonShrout · Post by **JonShrout** » Mon Jun 05, 2006 4:41 pm

I think I may have solved this.

The max memory usage on the SQL Server instance was set to 60% of max allowed. I bumped it back up to max allowed and the propagation time for the Shadow Folder went back to normal.

lbauer · Post by **lbauer** » Mon Jun 05, 2006 4:44 pm

Thanks for the update. I was going to have you enable logging, etc., but that mostly would have shown us the slowdown, not what caused it.

Shadow folders may take a minute or two to update, but 5 - 10 minutes usually means a network or SQL Server issue is slowing things down.