> When using MS Team Explorer to get latest (for the entire application)
> performance is less than 2 minutes - Very Acceptable
Can you describe this action? This is using the TFS client to do a "get" of
all the SR* files in the workspace? That's all it's doing right? It's not
calling the SCC API or doing file compares or object imports - just a simple
file copy over the WAN?
Have you tried experimenting with the Status Refresh Rate? That controls
the "freshness date" on each object. PB only runs the refresh status
operation on an expanded PBL if it sees that there's at least one "stale"
object in the PBL. So, to workaround slow SCC providers, some shops have
done the following:
- Set the Refresh Status Rate to 500 (just over an 8 hour day)
- When they sit down in the morning, do a target-wide refresh status (and
refill their coffee cup).
- Now PB will see every object as "within" the status refresh window, so it
won't run a Refresh on PBL expansion.
- However, this forces you to do manual Refresh Status requests yourself -
but you can do it at your leisure.
One other debugging effort - set SCCLogLevel=3 (verbose) to see more
information during SCC operations. Maybe the answer will lie in there.
--
Paul Horan[Sybase]
paulhoran.pbdjmagazine.com
"Mike" <mdowns_nospam@mile.com> wrote in message
news:49e48c08$1@forums-1-dub...
> We are attempting to integrate a PB 11.2 application with Team Foundation
> Server Version Control but are encountering major performance issues. Our
> environment is as follows:
>
> PB 11.2 build 8739
>
> MS Team Foundation Server 2008 Located remotely - No TFS Proxy
>
> Our application has 19 PBL's and approximately 4000 objects.
>
> When using MS Team Explorer to get latest (for the entire application)
> performance is less than 2 minutes - Very Acceptable
>
> If we attempt to do the same in PB ( even just a Refresh Status - Perform
> Diff on status Update is turned OFF) it takes over 10 minutes - Not
> Acceptable.
>
> Although this is a major issue the BIGGEST issue for us is when in the PB
> IDE and you attempt to expand a PBL by clicking on a node in the SysTree.
> PB does a Refresh Status which takes upwards of a minute or more depending
> on the items in the PBL to complete. During this time the developer cannot
> check out an object to work with.
>
> We currently have SCCMaxArray set to 250. We did some experimenting with
> this (we tried different values between 5 and 5000 with 5 performing the
> worst and 5000 not much better than 250)
>
> Any suggestions, explanations or even just verification that this is
> expect performance would be appreciated.
>
|