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

Jul 8, 2012 3:40 AM UTC

This is very very common enhancement for us.

Jul 9, 2012 8:20 PM UTC

I completely agree that this would be great.  The improvements I've seen in analysis tools such as CFDesign and Microstripes is amazing.  I also understand the difficulty in splitting an explicity sequential process into multiple-processor enviornment.

I don't know anything about Catia or NX 8, but I haven't seen that Solidworks makes any better use of multiple processors than Pro/E.

From Solidworks http://www.javelin-tech.com/main/support/solidworks_2012_hardware_faq.htm

"Only certain functions of SolidWorks can actually utilize multi-thread technology.  Running simulation analysis, rendering images, file opening and user interface activities (redraw, dialog boxes) can take advantage of multiple cores as there are multiple calculations that can be determined simultaneously."

Sep 18, 2013 7:16 AM UTC

I agree with that request! The ability to use multi-CPUs for model regeneration action in Creo 2.0 would be very helpful for us.

Jun 12, 2014 8:04 AM UTC

but must be

we will wait

Aug 13, 2015 7:37 AM UTC

As nowdays CPU's are getting more and more multi cores the clock frequency per core is mostly not rising so buying a CPU that is faster at a single core is becoming complicated.

Sep 1, 2015 12:49 PM UTC

While we're all waiting for PTC to make any sort of progress on this, I'll just leave you with this link:

PassMark CPU Benchmarks - Single Thread Performance

From the (very few) tests I've done, the numbers there seems to correlate pretty well with regen times.

Worth noting that single-thread speeds are still rising - and that Intel beats AMD every time.

Feb 5, 2016 7:41 AM UTC

As far as I know, no other CAD system makes use of multiple CPUs upon regeneration.

There are things that can be "parallelized" and there are things that can't. Yes, when you build a brick wall it will be faster if you have more people.

When you write a novel, it will pretty much mess up your story if several people write on it simultaneously.

Regenerating a feature tree is like writing a book. Feature X is dependent on feature Y and can't be processed until the latter one has finished regenerating. That's a serial process, not a parallel one.

In short: I doubt they will be able to do it. And IF, there will be tons of regeneration bugs and instabilities, so nobody would turn on that feature (presuming there would be a config.pro for this).

Feb 5, 2016 8:54 PM UTC

Personal experience with a large assembly (25'000 - 30'000 parts) showed creo/elements pro 5.0 to regenerate about 2-3 times faster than SolidWorks. That was 2-3 years ago. Current experience with SolidEdge 7 albeit with much smaller assemblies (couple hundred parts), it is way slower than ProE was. So I'm a bit suspicious about claims of other systems being much faster.

I agree with the request, multi-processor is the way to go. The models are getting bigger and bigger with ever more detailed information and the 1 THz processor is nowhere in sight. It is frustrating to wait 15-30 minutes while the Task Manager shows 12% CPU performance. If PTC really doesn't know how to do it (a big if), then they need to find out. In the meantime, optimize, optimize, optimize...

Apr 8, 2016 8:33 AM UTC

Creo is built multi core. not for regeneration like Herwig Scharz stated. but graphix go to seperate core, and in simulate Creo uses all the cores.

Apr 8, 2016 1:44 PM UTC

Getting any 3D CAD system to use multi-processors is the holy grail of the development teams at all vendors. Like Herwig said, you have to do operation X before operation Y, so it is a serial functionality which does not lend itself to being split. Passing the data to the graphics chip for rendering may be split. Mechanica computations and NC programing operations may be split, but only at certain points that the computer has to understand before it starts.

For straight CAD work, multiprocesors 'help' if you isolate the CAD process to a single processor core and use the others for your OS, email, word and net surfing.