With Simulation only so much of the calculations can be done individually because things like stress and how they travel through the mesh need to rely on other calculations and need to happen in order. Because the raytracing calculates light in small areas those areas can be sent to different cores. The reason for this is because a render can effectively be calculated over multiple cores. If you render, this is one area where as many cores as you can get help regardless of speed.
If you do a lot of simulations you can see some benefit to get 4 or 6 core machine with a fast processor speed. So in general, if you don't render, don't do simulations there is no reason to buy a ton of cores as they won't get used. More so that first core is typically shared with other stuff so if you run email, web browser, stream music etc you are robbing SW. So modeling, assembly creation, mates/motion, kinematics and all that stuff will only use one core. Other than sim and render, almost all of the normal stuff you do in Solidworks are single-threaded. To the point where i saw 5min render with 6 physical cores and a 4min render with 6 physical and 6 virtual. Even though its usually claimed it doesn't help i have seen jumps in Render performance by turning on Hyper threading giving me virtual cores. Rendering is one of those tasks that use multi cores systems well. More cores typically drop performance as the frequency is key. FEA, flow sim, thermal all benefit from 4-6 cores as fast as you can get. Certain functions in Solidworks make use of multi-core processing to split the calculations up.
0 kommentar(er)
