Performance: Number of Objects in Workspace

[BillRyan]

Why does the number of objects in a WindChill Workspace have such an impact on performance while working in Pro/E or Creo Parametric?  Our top level assemblies contain more than 60,000 objects, but we can only efficiently work with under 3000 of them in the workspace.  Users are trained to remove objects in the workspace to get performance back when the number exceeds the threshold.  As an example, the simple function of expanding the model tree can take up to 5 seconds waiting for the assembly to be downloaded from the server because it currenlty doesn't exist in the workspace.  I want the missing files in the workspace to be downloaded at the same rate whether there are 10 or 10000 objects existing in the workspace.  

[SteveShaw]

We are always looking to improve performance and scalability with each release of Windchill and Creo.  In 10.1 and Creo 2.0 we have made some changes to the data format we use when sending server responses to the workspace which should improve things for you.  However, in your case you are obviously working with assemblies and workspaces that we would consider as extra larger.  A few other recommendation to help with this large assembly management scenario would be to take advantage of the feature object filter in the workspace to limit how many rows are rendered in the browser, also leveraging external simplified representations and the 10.0 design in context capability to deliver only the data that is needed to the client.

[ChrisPLM]

Hi

I agree with Stephen. I can't imagine a user needed all the 60 ,000 files at the same time and working on them be it components changes, or assembly arrangement changing. Users should only had to their workspace object of interest either by using filters (Display WS as Featured Objects Lists) opening the right simplified representation.

If the user do need to see the full assembly, why not using ProductView (Creo View) ?

[GregoryPERASSO]

Agree ..

and what about "top down" or "design in context" features or methodologies ...

To be able filter and work by functionnal or zoning aera ...

[SteveShaw]

With the combination of Windchill 10.2 (recently released) and Creo 2.0 we have made significant performance improvements around working with large workspaces.

[tschweizer]

Stephen

In your Presentation "Windchill_10.2_CreoDataMgntUpdate Presentation of 10.2" there is a chart showing the performance improvements in combination with Creo 3.0.

So is there real lyalso improvement with creo 2 / WC 10.2?

Thank you

Thomas

[SteveShaw]

Yes.  The compatible maintenance releases contain the same performance improvements that have been developed for Creo 3.0 at the time of 10.2 release.

[JenniferPierron]

Hello.

PTC has done some further investigation about why large workspaces take more time to perform an action than smaller ones.  We found that after actions we "refresh" all sorts of information about the objects in the WS.  A significant amount of time is taken checking for and refreshing changes made outside of the workspace (I'll call these commonspace changes).

In Windchill11.0, PTC will introduced a new server-side preference to delay the refresh of changes made outside the workspace, and to update this information it in the background when the client is not in use.

Current performance testing is very promising.  Check out of a single object in a 20,000 object workspace improved by an average of 62% (in a testing environment)!

Please test the Windchill 11.0 behavior with the server-side preference Workspace > Update Commonspace Changes In Background.

Thanks

Jennifer

[hlinseisen]

Is Windchill 11 already downloadable or do you know any planned release date ?

[JenniferPierron]

Hello.

Windchill 11.0 is planned to be released at the end of the year.

Thanks

Jennifer

[BillRyan]

Thanks Jennifer!  We plan to be in WC11 by early next year and look forward to evaluating the performance improvements related to refreshing / interacting with workspaces.  Any improvements where Creo communicates with the server will be appreciated.  It's not specifically mentioned in your note above, but I hope the "call" for objects from Creo acquires the same 62% performance gain that the checkout transaction benefited from.