This is an old problem, not PFC-specific, not PB7-specific; I'm not sure,
but I think it got really bad until PB5.
We spent a not-so-small amount of money for a network expert to come in
and determine that PB opens and closes the PBL for each object it needs
until every object is cached, rather than caching the entire PBL the first
time. Or possibly it doesn't cache the PBL directories, and searches the
entire library search path every time. Either way, it appears to open the
PBL, read the PBL directory, navigate to the source and pcode sections, read
them into your PC's memory, then close the PBL. Then it repeats this (open,
read, search, read, close) recursively through the object's ancestry. Then
it repeats it (open, read, search, read, close) iteratively for each object
in the control array. You've probably noticed that the second time you open
a window, it is much quicker, and that the second instance of u_dw that you
add to a new window appears almost instantly, compared to the first.
This was exacerbated by our antivirus software (controlled by our network
group) scanning every file (including PBLs) upon opening. We now have the
PB developers in a group where only EXE/COM/MDB/XLS/DOC (and maybe some
other) files are scanned upon opening.
We got some improvement when we did away with a (mostly unused) "middle
layer". Even when the middle layer was empty, PB would have to search every
PBL for the ancestor. This entailed an (open, read, search, close).
We got some improvement by putting the PFC PBL's first, followed by PFE,
followed by application PBL's.
We ended up creating DOS batch files that would copy newer PBL's from our
network drive to the local drive. Developers use the network PBL for
checkout (to the copy in their local drive). We had to modify our process,
because obviously you need to run this "update" every time you check objects
back in (otherwise your local PBL does not have the change you just made).
--dang
P.S.
The key to the batch file is the "/d" parameter to the xcopy command, which
only copies files with a newer timestamp.
Here's a brute-force example:
update.bat:
C:
CD \APP\DEV\SRC
xcopy /d I:\APP\DEV\SRC\*.PBL
-----Original Message-----
From: Theisen, Timothy J. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 02, 2000 10:56
To: 'PFCSig'
Subject: PFCSIG PB 7.02 Build 8003 and PFC - Very Slow opening Windows
in IDE?
Anyone know if this is a PFC related problem or just the PB IDE? It takes
forever(1-2 minutes) to open windows and user objects when developing from
the network.
It is a little faster when working on the local machine. We are using
Pentium 350 mhz
with 128 meg ram. Thx.
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
