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

Jun 15, 2016 3:16 PM UTC

Is it a technical difficulties as for PTC? this is the highest voice requirement,it seems that PTC do not care it,and no one answer it

Jun 15, 2016 4:00 PM UTC

I have heard there is some multi-processing in Creo4, but doubt it will be a mind blowing improvement. CAD just does not lend itself to doing things in parallel. The best you can do is get the fastest chip in your computer. You can isolate tasks to certain cores so Creo has a 'dedicated' core, which may help, but this is a manual process after the applications are running. I used to do this on my Windchill server to put 1 Method Server on each core.

Jun 15, 2016 4:07 PM UTC

As Ben said, Creo 4 will utilize more multi-processing capabilities.

See Raphael's comment on this thread.

Feb 28, 2017 3:38 PM UTC

Hi,

I am maybe not an expert but I have to say that compared to NX and Solidworks, Creo is definitively slower 2x-3x times when importing STEP files.

I see it every day, because our clients have NX 10, Catia V5-6 2014, or Solidworks 2015 and when I work for them, I connect remotely to them via Teamviewer to discuss the manufacturing problems. They don't have native files, only STEP, so it's really simple to compare the results.

My PC is far far better than theirs (i7 Extreme Edition - 4700MHz, Quadro M2000, 256GB SSD), yet I need double the time as they do, to open the same STEP assembly with 2000+ parts.

Also when computing paths in CNC Milling, Creo uses only one core. This is killing me...and I don't want to start the discussion now what is better or worse, but the new ModuleWorks in C3 is definitively slower than Vericut too.

Feb 28, 2017 3:49 PM UTC

Hi Lukas,

I think STEP import may be off-topic here, unless Catia or NX use multiple cores when importing.

Do you have Windchill, or a long search path configured, when you import STEP files?  For large STEP assemblies, I believe Creo has to check the database or the search path for the filename of every part, before it imports it - this can cause significant slow-downs.  Catia at least seems to manage its files differently, so doesn't suffer from this issue.

Creo also seems to briefly create each file on disk then delete it again - this too could cost time for big assemblies, particularly if your working directory is across a network or on a slow disk.  It's another situation where I like to set my working directory to a RAM drive.

Feb 28, 2017 4:11 PM UTC

Hi Jonathan,

I don't agree, that it's off topic, because when concurrency (like Siemens, etc) can make the same thing faster and quicker, than I am as current PTC customer very motivated to jump on this train. If it was up to me, it would certainly happen long time ago.

To be more clear on my general problem with C3: imagine, that I have to import every day like 3-4 molds with 2000+ parts and I wait several hours compared to me concurrent company that can do this in half of the time. This is big disadvantage to me, when using Creo.

Also, I have compared the mentioned NX, Catia and Solidworks and they do seem to use more than one core at certain points. As I said, this is hard to analyze under Win7 and is only my personal opinion.

What matters is the difference when importing, regenerating and milling with creo compared to concurrency.

RAM Drive is not bad thing, but I doubt that it would help in my case, when one CPU-Core runs at 99% when importing STEP files.

To answer you question, we don't use Windchill.

Feb 28, 2017 4:34 PM UTC

I've just tested STEP import into Catia (V5-R20) with a 72 MB file, opening off a RAM drive to avoid any bottlenecking, and it ran on one core*, taking about 90 seconds.  I agree, from experience, that Catia is typically faster at importing STEP files, but it's not because it's multi-threading.

Why not open a new Idea to speed up STEP import?

Do you have a search path?  If so, how long is it?

*13% CPU usage of my quad-core, hyperthreaded processor, in the Win 7 Task Manager 'Processes' tab

Feb 28, 2017 4:59 PM UTC

Hi Jonathan,

72Mb is very small to compare CADs - as you said every SW is a bit different.

You will see very disappointing C3 results with 2000+ parts when importing. 3000+parts takes more than hour, sometimes even more than two.

To be more precise about my observation and results, I have tested C3 M110 very extensively last month with:

1.) import of 350MB STEP mold with 2000+ parts - Creo uses single core

2.) Renaming of one part after import - Creo uses single core (renaming takes up to 3 minutes with 2000+ parts!!!)

3.) NC path computation when milling - Creo uses single core

4.) NC Check with Moduleworks - Creo uses all Cores

I have observed, that with Hyperhtreding-OFF alone, I got +5% boost. With overclocking from 3.3Ghz to 4.7Ghz (and turning down-clocking off) I got +25% boost on average at all 4 tasks. I have not looked at benchmarks like CPU-Z for this purpose - those are only numbers at paper many times, but I have stopped time needed to complete all 4 tasks.

What did you mean with 13% usage exactly - one core or all four cores?

I have discussed my problems many times with Customer Service, but everybody pointed me to an CS-Article about "Creo Multi-threading capabilities" at PTC-website - that says nothing more than: "this is how it is with Creo - get used to it!"

Feb 28, 2017 5:13 PM UTC

Task Manager reports total CPU usage as a percentage of all the cores it counts.  With four cores and hyperthreading, there are eight logical cores so one core is 100 ÷ 8 = 12.5%, which displays as 12 or 13%.  If one process (here, either xtop.exe or cnext.exe) is reporting 13% CPU, then it's (effectively) using one core.  (If you display a separate graph for each core then you'll see Windows load-balancing across several cores, but this doesn't make the process run any faster than if it was locked to one core - they're just taking turns to process it.)

I'm not disputing that Creo is slower than Catia - my point was that Catia is faster but still only uses one core.  Therefore only using one core is not the reason that Creo is slow at this task; and also the writers of Catia have not found a way to multi-thread STEP import either.

Feb 28, 2017 6:27 PM UTC

Hyperthreading should be disabled when used on systems that do intense CPU processing, like CAD design. There is an inherent overhead in handling the extra thread on each processor that is actually slowing down the CPU core. I have had IT disable hyperthreading in the BIOS on CAD workstations and even the Windchill servers.

Importing STEP files is only a marginal method for comparing performance. Depending on the complexity of the geometry, the STEP processor could be storing hundreds of segments as it reads the STEP file before building the solid that is defined.