Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rhino:display_performance [2022/10/17]
maryfugier [Buy A GPU for the Right Reasons]
rhino:display_performance [2022/10/18]
maryfugier [Task Manager Performance Testing: Not the right tool]
Line 1: Line 1:
-====== Understanding Display Performance ======+====== Understanding Display Performance in Rhino ======
  
 ===== Question: ===== ===== Question: =====
Line 8: Line 8:
 //When I run the 'TurnTable' command and watch the performance tracking in the Task Manager everything is under 50% utilization (with the 2200 card the GPU was maxing out, with the A4000 it hits 44%).  //When I run the 'TurnTable' command and watch the performance tracking in the Task Manager everything is under 50% utilization (with the 2200 card the GPU was maxing out, with the A4000 it hits 44%). 
 However, Raytrace mode and hits 100% performance in Task Manager// However, Raytrace mode and hits 100% performance in Task Manager//
-{{:rhino:cpu_bottle_neck_01.jpg?400|}}+{{:rhino:cpu_bottle_neck_01.jpg?500|}}
 ===== 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.
-{{:rhino:cpu_bottle_neck_02.jpg?400|}}+{{:rhino:cpu_bottle_neck_02.jpg?500|}}
  
-Size of the file also has nothing to do with display performance, however **all** the geometry must be processed and meshed by the CPU before the GPU can take over. This can appear like the display performance is slow, when it is really a bottleneck at the CPU.+Size of the file also has nothing to do with display performance, however **all** the geometry must be processed and meshed by the CPU before the GPU can take over.  
 + 
 +**//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 112: Line 114:
 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 an new Italian super car … and get on the starting line…+I go out and I buy an new Italian supercar … and get on the starting line…
 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 sedan is the Intel and super car is the RXT Quadro+The crew is the CPU, and the car is the GPU. The older sedan is the Intel and supercar is the RXT Quadro
  
 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.txt · Last modified: 2022/10/18 by maryfugier