Skip to main content
Jul 8, 2012 3:26 AM UTC
Under Consideration

Support multi-CPUs(processors) for model regeneration action in Creo

Related products:Creo Parametric

Idea Message ID:  8127

 

Now most customers are using multi-CPUs(processors) machines.

But for creo current release, only support multi-CPUs(processors) for graphics area and mechanica mode. Buy expensive machine and expensive software, it is very waste for us.

As I know, NX 8.0, solidworks 2012 and CATIA are support multi-CPUs(processors).

35 replies

Feb 28, 2017 6:41 PM UTC

First, I know what cores and HT means. You didn't say you have activated HT. I have disabled HT because of Creo and use only 6 logical cores out total 12.

I don't want to disagree with you. Everybody can compare Creo with other product for himself. I am only posting my observation and tests.

I don't want to have dispute about if Catia (or other SW) is better than Creo or if other CAD-SW can use more than one core. Not my point.

What is obvious to me, that Catia with one core can outperform Creo (and NX and Solidworks too).

What is more disturbing is, that company I work for, can't compete with other companies (in the same business) using Catia, NX or Solidworks, because I sit behind my PC waiting on Creo to import STEP-files, whereas other companies use this time to work with the already imported files and are productive.

And this was my original point.

Feb 28, 2017 6:44 PM UTC

Thank you Ben, I think and have tested the same: with HT-off most CAD-SW (and Creo too) are faster.

Mar 1, 2017 8:57 AM UTC

Well, I said it was "quad-core, hyperthreaded", so that kind of implied I had HT enabled; and you'd said "this is hard to analyze under Win7" and "What did you mean with 13% usage exactly - one core or all four cores?" so I was trying to explain in more detail.

And my original point was that improving the performance of STEP import should be a separate discussion or Idea, not lumped under one about multi-threading, especially as it appears that multi-threading is not the secret to STEP import.  If you have a specific subject such as this, then create a specific discussion so that all relevant aspects can be considered, not just one assumed solution.

You still haven't answered my search path question, btw - I'm pretty sure this can make a significant difference.

Mar 1, 2017 9:20 AM UTC

Hi,

Than we could separate discussion like: why is Creo using one core when milling, or why is Creo using one Core when regenerating, or why is Creo using one core when you rotate model in Wireframe and so on!

It's still the same product but everybody uses different modules in C3. Where is the point in starting 10 threads about the same topic?

Also Jonathan, this topic starts with words:"Buy expensive machine and expensive software, it is very waste for us". This is true for everybody who uses Creo - no matter what you do with it. For you, is importing of STEPs or CNC Milling maybe of no interest, but for other people like me, it's "daily bread" and speed of SW is essential to stay competitive.

We don't use search-paths now. If you have some suggestions, I would be glad if you instruct me. So you know, 100% of our work is to open STEPs  with 2000+ parts locally on SSD and make som CNC milling. Two day work mostly. So I don't know how search-paths could enhance this kind of work.

Mar 1, 2017 9:26 AM UTC

No, if you don't use search paths then that's best for STEP import.  Using a long search path, as I said originally, can slow the import further.

Mar 1, 2017 9:31 AM UTC

So I thought. Thanks for reassuring me.

Jun 14, 2018 6:13 PM UTC
Status changed to: Acknowledged
Mar 18, 2019 11:31 AM UTC
As a first step towards improving CPU core use, could drawing view regeneration and ModelCHECK processing be updated to process each view (or at least sheet for ModelCHECK) in a separate thread?
Community Manager
Sep 19, 2019 4:33 PM UTC

Idea Message ID:  8127

 

Now most customers are using multi-CPUs(processors) machines.

But for creo current release, only support multi-CPUs(processors) for graphics area and mechanica mode. Buy expensive machine and expensive software, it is very waste for us.

As I know, NX 8.0, solidworks 2012 and CATIA are support multi-CPUs(processors).

Jun 24, 2020 4:29 PM UTC
Status changed to: Under Consideration

PTC is researching the ability to support Multi-threading for regeneration.  There is no commitment on time frame, but PTC is investigating the efforts to provide such support in a future release of Creo. 

 

In the meantime, PTC has introduced a number of functions within Creo that are currently multi-threaded such as:

  • Model Retrieval
  • Tessellation - this is used as part of retrieval, but also when changing shade quality of model
  • Lattice Generation
  • Generative Design - This also takes advantage of GPU (NVIDIA Cuda-based cards)
  • Creo Simulation Live - GPU processing (NVIDIA Cuda-based cards)
  • Render Studio - In the future will also take advantage of GPU (NVIDIA Cuda-based cards)
  • Hidden Line Removal
  • Creo Flow Analysis
  • Reconstruction - Part of Generative Design and Freestyle

All new development includes research into leveraging threading to help improve performance and take advantage at the available hardware.  Once such area is graphics, which will introduce performance improvements in all areas of Creo.

 

Lastly, PTC will be reviewing the listed areas currently supporting Multi-Threading and improve their scalability to maximize the available resources in the users machine.

 

Regards,

Mark Fischer

Sr. Director, CAD Product Management