To be fair(er) to PTC, the multicore support in HSM doesn't seem to apply to the CAD application but only to the CNC path generation segment that was purchased as part of Autodesk buying HSM from under Dassult's reach.They also support splitting the NC path generation to entirely different machines. It's relatively easy to do for NC path generation. Calculating the roughing pass and the final pass for each feature can be done independently. Creating paths for drilling and tapping doesn't depend on milling calculations. Paths for separate sides of the parts are also independent.
It's an interesting problem as described here http://www.3dcadworld.com/solving-cad-concurrency-problem/
In the comments on concurrency a statement is made that D-Cubed is multicore capable (it says version 58 (2D), but I found a ref in 47(3D)), which the D-Cubed site http://www.plm.automation.siemens.com/en_us/products/open/d-cubed/product_news/3ddcm_version47.shtml indicates that it is only thread safe, not managed distribution."From this version 3D DCM creates a series of independent discrete tasks, each representing a portion of the requested calculation. These tasks are passed to the application which can then run them using any desired parallelization technique."
In other words, if the running application can figure out some way to manage the parallel tasks, D-Cubed routines can be dispatched to separate cores. It still leaves scheduling and setup of those tasks to the host software. Scheduling and setup are the hard part of parallel execution.
In looking through release notes, it's interesting to see the sort of controls that D-Cubed offers software developers. I liked the one on chirality controls. These prevent the obnoxious flipping between solutions by adding more refined controls to detect a change between shapes that otherwise meet explicit geometric constraints. http://www.plm.automation.siemens.com/en_us/products/open/d-cubed/product_news/2ddcm_version62.shtml
