What goes behind the screen of NX application while loading CAD model

[NXsupport]

Hi,

NX8.5..

TC 8.3

Is there any document which gives idea on what is going when I click a UGPART dataset to load into NX.. Iam looking for a slide or document which gives some approximate information on how NX starts to load the CAD model.. What goes behind the screen ..

I have seen, sometimes, the loading times are fast, closing times are slow etc other times its the reverse case.. sometimes, both are slow..

Any help is highly appreciated..


NX support

 

[JohnRBaker]

No, there's nothing like that. It would be of little value to anyone not working on the NX code itself.

Now there are various Load and Save Options which can impact the time it takes to open and close files. It also depends on whether you're opening an Assembly or s simple piece part. Also when you Save your parts, again it depends on whether you're saving an Assembly or a piece part. In the case of any Assembly one time you may have only modified the Assembly and none of the Component parts where another time you may have several parts open which have been modified and so when saving it will take longer.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[Nham]

Hello John,

It is easy to disagree to your statement. But also true that many things are controlled by customer defaults and so on. Those settings controlled from site level should give peace to test with site settings. Some things still are not controlled by site settings so it is not bulletproof.

Sometimes nx loads and saves are affected by database and network conditions plus also teamcenter settings like additions to nx-tc attribute mapping.

For nx admins it is frustrating to put all logging options on and still only have 10% of things there. But as said, that is considered more to belong to some other category like infra or database dba area.

I have seen huge performance variations between nx7.5 sites without being able to pinpoint exactly why the other site is slow. All configurations are the same but the assembly open takes longer on the other site. Because this is tc dependent and network dependent it is hard to know why.

Still, users see their nx first and ask why is this taking longer than yesterday.
Usually you start the investigarion from the nx side. It would not hurt to have a performance monitor for admins that you can run comparisons against baseline embedded in nx. That way all tests would be more reliable and repeatable.

Like a user friendly collection of logging events in a context of your test assy.
Always done with same set of data with a network and sql query numbers right next to file load times from network.

That would be something worth of having. Even with additional cost and license fee.

BR,
NH