Hello Marty,
there is no such a thing like "general speed", which can be slower or faster in Creo, like it would be with a game or when playing a video or when doing a benchmark.
There are very diverse models, use cases and run settings on one side and there are different bottlenecks on the other, like for example:
- When regenerating complex parts, the CPU speed is crucial - multiple CPUs don't help much.
- But when doing Photorendering or Simulation calculations in Creo, speed almost scales with the number of CPUs.
- When spinning shaded models, only the graphics card makes the difference, CPU is irrelevant
- When spinning in hiddenline or no hidden mode, it is just the opposite, CPU speed counts
- When running out of system memory or out of dedicated graphics memory, the computer starts paging (swapping) lowering performance about factor 5-10(!)
- Processes that frequently write to disk are slowed by disk speed and if they write to mapped drives this can become really tedious.
- Stalled internet connections (e,g, in the internal browser, but sometimes just an OS process in the background of the OS) can make a session hang for several seconds
- Of course there are any number of mixed cases as well.
Hence all you have been told about network, memory, graphics card, etc., is surely correct in one or more contexts and irrelevant in others - this is what makes it so difficult.
As a consequence, when troubleshooting performance being slower than expeced, the first thing is to evaluate, what exactly are the actions and the environment, what are your expectations and what is the observed speed.
Only then a meaningful diagnosis and recommendations are possible.
For example:
- For the original concern with slow spinning, I'd guess the graphics is hidden line or nonhidden, which will not make much use of the graphics and calculate the hidden lines by CPU.
- As for Silvain's observation: Creo spins "real" geometry you can model if you want, while Productview is only using a mockup (triangulated surfaces), which is quite faster for displaying.
Regards,
Gunter
