Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
rhino:display_performance [2022/10/14] maryfugier [What else slows down the performance] |
rhino:display_performance [2022/10/18] (current) maryfugier [Task Manager Performance Testing: Not the right tool] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Understanding Display Performance ====== | + | ====== Understanding Display Performance |
| ===== Question: ===== | ===== Question: ===== | ||
| Line 7: | Line 7: | ||
| //When I run the ' | //When I run the ' | ||
| - | However, Raytrace mode and hit 100% performance in Task Manager// | + | However, Raytrace mode and hits 100% performance in Task Manager// |
| + | {{: | ||
| ===== Answer: ===== | ===== Answer: ===== | ||
| Line 15: | Line 15: | ||
| Let's look at some of the issues with using Task Manager to measure performance. | Let's look at some of the issues with using Task Manager to measure performance. | ||
| - | Cycles 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 |
| + | {{: | ||
| + | |||
| + | Size of the file also has nothing to do with display performance, | ||
| - | Size of the file also has nothing to do with display performance, | + | **//This can appear like the display performance is slow, when it is really a bottleneck at the CPU.//** |
| ==== The CPU Bottleneck ==== | ==== The CPU Bottleneck ==== | ||
| Line 35: | Line 38: | ||
| This is what is happening when the Render display model reports 27% or similar number for GPU performance. It is not that the GPU is the issue, it is simply waiting for the CPU to catch up. | This is what is happening when the Render display model reports 27% or similar number for GPU performance. It is not that the GPU is the issue, it is simply waiting for the CPU to catch up. | ||
| + | [[https:// | ||
| ==== Similar Geometry: Instancing in the Display ==== | ==== Similar Geometry: Instancing in the Display ==== | ||
| If those 100K objects all looked the same, then Rhino could draw all of them in one fell swoop using a single call to the GPU. | If those 100K objects all looked the same, then Rhino could draw all of them in one fell swoop using a single call to the GPU. | ||
| Line 42: | Line 46: | ||
| 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 ==== | ||
| Line 83: | Line 87: | ||
| Apply the above procedure first, steps 1-4. | Apply the above procedure first, steps 1-4. | ||
| Of course keep all the polysurfaces hidden. Hide everything but the Meshes. | Of course keep all the polysurfaces hidden. Hide everything but the Meshes. | ||
| - | 5. Selmesh | + | - Selmesh |
| - | 6. Join | + | - Join command |
| - | 7. Turntable | + | - Turntable |
| // | // | ||
| You now have only 1 large mesh// | You now have only 1 large mesh// | ||
| Line 101: | Line 105: | ||
| Buying a new GPU will most likely not provide any improvement for models that bottleneck on the CPU. | Buying a new GPU will most likely not provide any improvement for models that bottleneck on the CPU. | ||
| - | The model is still going to bottleneck on the CPU and the GPU will just sit there waiting | + | The model is still going to bottleneck on the CPU and the GPU will just sit there waiting. |
| - | Let me make a draft reply and you can review. I think I have enough here. | + | |
| === The Race Car Analogy === | === The Race Car Analogy === | ||
| - | I have a standard Toyota Civic sitting at the starting line. I can’t “go” until all of my tires are changed, and my tank is filled with gas… | + | {{: |
| + | |||
| + | I have a 90's 4-dr sedan sitting at the starting line. I can’t “go” until all of my tires are changed, and my tank is filled with gas… | ||
| It takes my pit crew 8 minutes to get everything ready. And then floor it, and it takes me 15 seconds to reach the finish line… So the overall time it took was 8:15 (8 minutes, 15 seconds). | It takes my pit crew 8 minutes to get everything ready. And then floor it, and it takes me 15 seconds to reach the finish line… So the overall time it took was 8:15 (8 minutes, 15 seconds). | ||
| - | I go out and I buy a Ferrari | + | I go out and I buy an new Italian supercar |
| My crew still takes 8 minutes to get everything ready… I then floor it, and it takes, me less than 5 seconds to reach the finish line (300% faster)… The overall time it took was 8:05 (8 minutes, 5 seconds)… | My crew still takes 8 minutes to get everything ready… I then floor it, and it takes, me less than 5 seconds to reach the finish line (300% faster)… The overall time it took was 8:05 (8 minutes, 5 seconds)… | ||
| - | The crew is the CPU, and the car is the GPU. The Honda Civic is the Intel and Ferrari | + | The crew is the CPU, and the car is the GPU. The older sedan is the Intel and supercar |
| If you really want Rhino to be faster, you will need to first invest in a faster CPU… Then augment that with a better GPU. | If you really want Rhino to be faster, you will need to first invest in a faster CPU… Then augment that with a better GPU. | ||
rhino/display_performance.1665791866.txt.gz · Last modified: 2022/10/14 by maryfugier
