Does the time Wildfire locks up during a workspace sync depend on how
many items are in the active workspace or does PDMLink take into account
all other workspaces and their object count?
I was working with a user who had 81 objects in the workspace and was
doing a revise. The system revised a related object it shouldn't have
and I when in a deleted that newly created revision. That caused the
workspace to sync since an item was removed from the workspace on the
server side. Wildfire (or IE) did its typical impression of water at
zero degrees. Local client remains idle during this time. After a few
minutes, I then noticed a very large network traffic spike. I have come
to expect this as the eventual response from PDMLink, downloading all
the workspace cache information. It seemed exceptionally large given the
size of the workspace.
Now, it might be that the system was especially busy at that time. I
would agree but this was repeatable over some time period and it is not
untypical. The user in question had 57 other workspaces full of
"important" stuff. So what is the major factor driving the long lockup
we experienced?:
* Server congestion
* Number of workspaces
* Number of items in all workspaces
* Number of items in active workspace only
* Some other reason
If anyone can think of test to eliminate or confirm one of the above
cases, let me know.
PDMLink 9.1 M020 and Wildfire 4.0 M110
