×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

low CPU usage, slow NX

low CPU usage, slow NX

low CPU usage, slow NX

(OP)
Gouge checking takes long time, but none of the CPU cores utilized 100%.
It is a Core2Quad, win7x64, nx8.0.3.4
What can be the reason?

----
kukelyk

RE: low CPU usage, slow NX

This has been discussed here and on other boards dozens of times. Using the Windows tools, if you have a multicore system, you will NEVER see any one core being reported as 100%. The maximum will be reported as 100 divided by the number of cores. In other words, if you have a total of 4 cores, at best Windows will report that each core is running at 25% capacity, that is to say that it's the SUM of the utilization of each core which will give you the overall SYSTEM utilization.

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.

RE: low CPU usage, slow NX

(OP)
Other times the memory usage flies to the sky. A simple planar mill operation, and a 30Mb model, gouge check with toolholder. The memory usage is +7GB..Why??

----
kukelyk

RE: low CPU usage, slow NX

kukelyk, can you please explain your question. There are many variables that affect memory usage - size of the model, resolution of the IPW used for collision and gouge checking, tolerances, etc.

Mark Rief
Product Manager
Siemens PLM

RE: low CPU usage, slow NX

(OP)
I have used NX for 8 years. I have recently changed to NX8. The settings are the same as in NX6, what I used on XP32, with 3GB RAM. The modelsize is also similar. I have never seen such a slow collision check, and such a slow NX
Animation accuracy: Coarse
The IPW resolution settings:
Coarse 400
Medium 700
Fine 1400

Gouge tolerances:
Gouge 0.01
Collision 0.5
Excess 0.1
Chordal 0.05
Tool axis tilt 0.05

These numbers are not so irreal, I think

----
kukelyk

RE: low CPU usage, slow NX

It should not be substantially slower unless we are checking much more.
If you think the collision check settings are the same as before, and it still takes much longer, please log a call with GTAC so somebody can take a look at it.

Mark Rief
Product Manager
Siemens PLM

RE: low CPU usage, slow NX

In 8 a new, more accurate, gouge checker is used by default. Supposedly it's more reliable in some cases where issues slipped by but our site never had major issues with the old checker which was quicker. If you want to use old gouge checking then use the variable UGII_CAM_GC_USE_OLD_CHECKER (value=1) but use it at your own risk. Siemens has told me the default nx8 gouge checking is recommended over the old method.

NX8

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources