Speed of background updates.

StuartHemming · Post by **StuartHemming** » Wed Mar 19, 2008 1:26 am

I wondered if their had been a change, in 4.1, to the frequency of the background updates.

I ask 'cos one of my colleagues and I have both noticed that changes, either to our local change set or to the files listed on the search tab, seem to take longer to show.

I've found myself using F5 more frequently since the upgrade; beforehand I rarely felt the need to bother.

ian_sg · Post by **ian_sg** » Wed Mar 19, 2008 3:40 pm

It sounds like you're talking about the stand-alone client. There's been no change to the background update frequency (which is configurable in the options).

I might need to narrow the focus a little bit to come up with a constructive response.

What kinds of changes seem slower to update?

I'll take a couple of stabs, in the mean time. If it's modified files that don't show up as fast, and you're not using checkouts, this can be caused by having more working folders set. With checkouts disabled, Vault has to scan each working folder for changes.

If you've enabled ghosted files and (in particular) folders, that can also slow down the scanning process some.

StuartHemming · Post by **StuartHemming** » Thu Mar 20, 2008 1:28 am

ian_sg wrote:It sounds like you're talking about the stand-alone client.

I am.

ian_sg wrote:There's been no change to the background update frequency (which is configurable in the options).

I didn't know that. Where?

ian_sg wrote:What kinds of changes seem slower to update?

Programmer A saves some changes to a file and the edited file doesn't show up straightaway in his pending change set. Or, Programmer A commits some changes but programmer B doesn't see them in the search window (looking for OLD files) as soon as he might expect.

ian_sg wrote:I'll take a couple of stabs, in the mean time. If it's modified files that don't show up as fast, and you're not using checkouts, this can be caused by having more working folders set. With checkouts disabled, Vault has to scan each working folder for changes.

Well, we're using Edit/Merge/Commit so that adds up. Although we were doing that before the upgrade too.

ian_sg · Post by **ian_sg** » Thu Mar 20, 2008 7:50 am

StuartHemming wrote:I didn't know that. Where?

It's in the general options. I attached a screenshot below.

StuartHemming wrote:Programmer A saves some changes to a file and the edited file doesn't show up straightaway in his pending change set. Or, Programmer A commits some changes but programmer B doesn't see them in the search window (looking for OLD files) as soon as he might expect.

If you have lots of working folder assignments and/or ghosted files/folders turned on, that can introduce some delay before a modified file appears. If you have a large tree, it's often easier to use the command line client to list all your working folder assignments to see if there are old ones you can remove. If you click the Rescan Working Folders button above the pending change set, do the modified items show up quickly?

The delay experienced by programmer B here would be primarily the result of the refresh interval. That update happens only when there's a refresh, which you can do manually (as you've already mentioned) with F5. Lots of other operations (e.g. Checkout or Get) also perform a refresh. The background refresh happens every 10 minutes by default (which hasn't changed), but you can decrease that if you'd like.