Differences

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

--- rhino:display_performance [2022/10/17]
maryfugier [The CPU Bottleneck]
+++ 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 in Rhino ======
 ===== 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%).
 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: =====
@@ 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.
-{{: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 ====

McNeel Wiki

Site Tools

Differences

Page Tools