This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
rhino:display_performance [2022/10/17] maryfugier [The CPU Bottleneck] |
rhino:display_performance [2022/10/17] maryfugier [Task Manager Performance Testing: Not the right tool] |
||
---|---|---|---|
Line 8: | Line 8: | ||
//When I run the ' | //When I run the ' | ||
However, Raytrace mode and hits 100% performance in Task Manager// | However, Raytrace mode and hits 100% performance in Task Manager// | ||
+ | {{: | ||
===== Answer: ===== | ===== Answer: ===== | ||
Line 16: | Line 16: | ||
Cycles Raytrace mode uses 100% GPU for everything it does, so of course it’s going to max out most of the time. (Turntable is not designed to work with Cycle’s Raytrace mode.) Raytrace is using the GPU 100% even though the display may still seem slow. | Cycles Raytrace mode uses 100% GPU for everything it does, so of course it’s going to max out most of the time. (Turntable is not designed to work with Cycle’s Raytrace mode.) Raytrace is using the GPU 100% even though the display may still seem slow. | ||
+ | {{: | ||
- | Size of the file also has nothing to do with display performance, | + | Size of the file also has nothing to do with display performance, |
==== The CPU Bottleneck ==== | ==== The CPU Bottleneck ==== | ||
Line 43: | Line 44: | ||
Obviously, it can be a bit more complicated, | Obviously, it can be a bit more complicated, | ||
- | **The GPU will almost never be the bottleneck for Rhino’s display, especially high-end models. Most of the time spent drawing things is done in Rhino’s object and attribute/ | + | //The GPU will almost never be the bottleneck for Rhino’s display, especially high-end models. Most of the time spent drawing things is done in Rhino’s object and attribute/ |
Rhino has tried to improve this over the years by packing as much as possible on the GPU, but there’s still the problem with the CPU just iterating over large datasets in general. | Rhino has tried to improve this over the years by packing as much as possible on the GPU, but there’s still the problem with the CPU just iterating over large datasets in general. | ||
- | **The typical recommendation for those with these issues is to first improve your CPU (more cores and higher processing speed), add more system memory, then improve your graphics card.** | + | //**The typical recommendation for those with these issues is to first improve your CPU (more cores and higher processing speed), add more system memory, then improve your graphics card.**// |
==== Mesh First - Then Render ==== | ==== Mesh First - Then Render ==== |