[Jo...] Posted November 26, 2025 Share Posted November 26, 2025 Hello, i have to do some mesh editing due to (allowed) burr that leads not calculated or misscalculated elements. I realised that some calculations are only running on 2-3 (from 16/32 cores) cores while others use all cores. In this case that amounts to just around 5% cpu usage total. Is there a way to optimize cpu usage? Link to comment Share on other sites More sharing options...
[Jo...] Posted 7 hours ago Author Share Posted 7 hours ago So is this "normal" behaviour? There is short spike at the start of recalculation of the project, then it goes back to using 3 cores mildly. Running a CPU bench. I get 98% load on way higher clocks for quite some time stable, so it is no hardware problem. Ram is used 1/5. Link to comment Share on other sites More sharing options...
[Ma...] Posted 5 hours ago Share Posted 5 hours ago ZEISS Inspect may not utilize all cores, but just a few - multithreading is a difficult task to program. This should be normal behaviour. Applied also to Calypso Many games do the same. Link to comment Share on other sites More sharing options...
[Jo...] Posted 5 hours ago Author Share Posted 5 hours ago Hi Martin, thanks for your reply. I get the challenges of multithreading. I started out in IT. Strangly not even single core performance is maxed out. Core clocks are well under max. And why calculation of stages is not parallelized is also not intuitivly understandable for me. Well i guess it is what it is 🙂 Link to comment Share on other sites More sharing options...
[Ma...] Posted 2 hours ago Share Posted 2 hours ago What you can do is boosting performance by using GPU and in the Inspect settings check "Use all resources" or something similar to use as much as needed. In 2025 and 2026 is this settings renamed. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in