cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X

Make the xtop process multithreading

Make the xtop process multithreading

Because there is no such multithreading mode for the xtop process. This makes Creo Parametric much slower in opening IGES,STEP, ... files the other CAD Software. 

 

 

3 Comments
StephenW
23-Emerald II
BenLoosli
23-Emerald II

For those asking for a multi-threaded xtop, explain how it should be done.

 

Pro/Engineer, Wildfire and Creo are parametric 3D modeling tools that store the data in a hierarchical arrangement 'database' within the part or assembly files. This means that before feature 305 can be placed in the model, features 1-304 must be created sequentially so feature 305 knows where it goes and what it interacts with. It is this sequential process of building the model that limits multi-threading of xtop. There are some areas that can be 'divided' (NC tool paths, FEM, shading, etc) and these do utilize multi-threaded processes spawned off from the main xtop.

S_Edgenear
14-Alexandrite

What should be done is not making xtop multithreaded, but allow it back to be able to be "multi-session", as it used to be. In several releases back, we could open two instances of PTC Creo (or wildfire, I think the problem started with the first release of Creo). In the second instance we could start an import session of a Step or Iges file, and could continue to work in the first session. Currently, we can still open several Creo sessions, but when the software is importing and calculating if the imported geometry can be converted to a solid, we are effectively blocked from continuing work in the first session since the importing thread is working at 100% in a processor core thread. Since the two Creo sessions have nothing to share or in common between both, there should not be present any multi-threading and syncronization problem between the internal database between the two sessions. What seems to happen is that the import geometry thread is always "pinned" or "allocated "to the same physical processor core that is used to do the regeneration on the first Creo session. The behaviour before was not this one. Whether this is made by design, as a bug, or it has to do with the license management between sessions I don't know, but we used to have fixed license options, so, we should not have artificial number of licenses that we could have open in the same machine. Even with a floating license, it does not make sense. There are times when we could use an aditional floating license to not stop working when importing complex STEP / IGES parts, if we have at lease on aditional floating lisense available.