Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
rhino:5:video:troubleshooting:slowrenderingmode [2022/02/03] maryfugier |
rhino:5:video:troubleshooting:slowrenderingmode [2022/02/03] (current) maryfugier [File Analysis] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Troubleshooting Slow Render Mode Performance ====== | ====== Troubleshooting Slow Render Mode Performance ====== | ||
| + | Back to [[https:// | ||
| ===== Question: ===== | ===== Question: ===== | ||
| - | I wonder why Rhino for instance cannot draw more Power from my graphics card running on only 35Watts whereas it could potentially draw 150-160Watts. GPU usage is 11%-22% depending on the display mode? | + | How can I make Rhino 6 or 7 use my GPU to its full potential? |
| - | | + | //"I wonder why Rhino for instance cannot draw more Power from my graphics card running on only 35Watts whereas it could potentially draw 150-160Watts. GPU usage is 11%-22% depending on the display mode? For me, this is what I get:// |
| - | | + | \\ |
| - | + | //Arctic viewport: GPU draws 30 Watts has an GPU utilization of around 10% and gives 6FPS// | |
| - | How can I make Rhino 7 use my GPU to its full potential? | + | //Shaded viewport: GPU draws 35 Watt has an GPU utilization of around 22% and gives 30 FPS//" |
| ===== Answer: ===== | ===== Answer: ===== | ||
| Line 16: | Line 16: | ||
| If your GPU is only drawing 35W, when it’s designed to support up to 150W, then it means that it’s operating at roughly 20% capacity. | If your GPU is only drawing 35W, when it’s designed to support up to 150W, then it means that it’s operating at roughly 20% capacity. | ||
| - | You may be expecting that “If something takes 10 seconds, then if I get a card that’s 10x faster, then it should only take 1 second”. | + | You may be expecting that //“If something takes 10 seconds, then if I get a card that’s 10x faster, then it should only take 1 second”.// |
| + | \\ | ||
| This is only true if 100% of the time Rhino spent on the GPU, which is not the case. | This is only true if 100% of the time Rhino spent on the GPU, which is not the case. | ||
| But if only 1% of the time is spent on the GPU, then the result is basically going to be the same…10 seconds. | But if only 1% of the time is spent on the GPU, then the result is basically going to be the same…10 seconds. | ||
| - | Why? | + | **//Why?// |
| - | This is because the problem (or bottleneck) is not with the GPU, so speeding up the GPU, or replacing it with a much faster one, isn’t going to do a thing. | + | This is because the problem (or bottleneck) is not with the GPU, so speeding up the GPU, or replacing it with a much faster one, isn’t going to do a thing.** |
| - | Start with the Model | + | ==== Start with the Model ==== |
| - | Getting a model is the best way for us to know where the bottlenecks are. So thank you for providing that file, we discuss | + | |
| + | Getting | ||
| + | You can submit a model for testing to tech support [[https:// | ||
| + | \\ | ||
| + | //(Fill out the comment field in the upload with all the details, so we know what issue you are having and what version of Rhino you are using. Incomplete information can result in a delayed response from technical support.)// | ||
| + | |||
| + | For example, if you are getting 3 fps Rendered mode result and a Shaded mode yields ~50 fps, that does seem concerning. | ||
| + | |||
| + | Without knowing what is in your model, we would guess that it's probably something to do with his object management, blocks, and lighting or some combination of both The use of multiple lights can have an abysmal performance. | ||
| - | Your 3 fps Rendered mode result does seem odd, given that his Shaded mode yields ~50 fps… Without knowing what is in your model, we would guess that it's probably something to do with his object management, blocks, and lighting or some combination of both The use of multiple lights can have an abysmal performance. | ||
| You will first need to first eliminate the typical CPU bottlenecks in the file geometry and setup, before you can expect good GPU performance. | You will first need to first eliminate the typical CPU bottlenecks in the file geometry and setup, before you can expect good GPU performance. | ||
| Line 36: | Line 44: | ||
| Trying to determine overall GPU usage on a single frame would be like trying to determine how fast your car’s top speed is by measuring how fast it takes it to move one inch from at rest position, and then extrapolating that into miles per hour. Not a good approach to finding the best answer. | Trying to determine overall GPU usage on a single frame would be like trying to determine how fast your car’s top speed is by measuring how fast it takes it to move one inch from at rest position, and then extrapolating that into miles per hour. Not a good approach to finding the best answer. | ||
| - | A better way (but still flawed), is to use the Rhino' | + | A better way (but still only an approximation) is to use the Rhino' |
| There is a Hollomark for specifically | There is a Hollomark for specifically | ||
| We do not write or support it, but it can be useful. | We do not write or support it, but it can be useful. | ||
| ==== File Analysis ==== | ==== File Analysis ==== | ||
| - | + | Here are some recommendations | |
| - | If you file appears | + | - Keep the overall number of objects in the scene as low as possible and not excessive |
| - | + | - Organize your file in and assign “objects” to “layers”. | |
| - | Also keep the overall number of objects in the scene as low as possible and not excessive | + | - Check for bad objects and rebuild them. |
| + | - Avoid excessive usage of blocks | ||
| + | - Purge unused content in your file like materials and textured. | ||
| + | - Reset your Render mode settings to default //(Options -> View -> Display modes -> Rendered. Pick button at bottom to reset to Rhino defaults.)// | ||
| + | - Insert the contents of your file into a new file. //(This may leave some problem with the file behind.)// | ||
| + | But still, the display performance can seem sub-par and painfully slow. | ||
| If different “shaded” display modes all seemed to produce similar performance results, **except the Rendered display mode** which can be significantly slower than the other modes. | If different “shaded” display modes all seemed to produce similar performance results, **except the Rendered display mode** which can be significantly slower than the other modes. | ||
| Line 50: | Line 63: | ||
| ==== Rendered Mode ==== | ==== Rendered Mode ==== | ||
| - | The focus was then turned towards | + | Now you can focus on the Rendered mode results to determine why and where things were slowing down. |
| - | Your file provided us with one of the more perfect examples of how to bring Rhino’s rendering pipeline to a standstill. | + | Many well organized files with no bad geometry can bring Rhino’s rendering pipeline to a standstill. |
| - | There are thousands of objects referencing several dozens of materials, many of which contain “transparency maps”. | + | |
| + | Another reason is transparency maps. There can be thousands of objects referencing several dozens of materials, many of which contain “transparency maps”. | ||
| Why is this problematic? | Why is this problematic? | ||
| Line 69: | Line 83: | ||
| However, the path from a Rhino object to colorful pixels on the screen is a very complex and tedious process that does not take place in these other products. | However, the path from a Rhino object to colorful pixels on the screen is a very complex and tedious process that does not take place in these other products. | ||
| - | TwinMotion and similar products are only interested in two things; | + | TwinMotion and similar products are only interested in **two things**; |
| + | - Polygons | ||
| + | - The color of said polygons. | ||
| + | Once they have all of the information for all of the polygons, there are all kinds of optimizations that can be made. | ||
| ==== Testing and Analysis ==== | ==== Testing and Analysis ==== | ||
| Line 91: | Line 108: | ||
| //This GPU graph above shows the same file with the optimizations explained above.// | //This GPU graph above shows the same file with the optimizations explained above.// | ||
| - | With these graphics, you can see the huge difference in GPU utilization, | + | With these graphics, you can see the huge difference in GPU utilization, |
| | | ||
| ==== In conclusion ==== | ==== In conclusion ==== | ||
| Line 104: | Line 121: | ||
| With that said, we are committed to solving the issues mentioned above over time, and are always trying to make changes/ | With that said, we are committed to solving the issues mentioned above over time, and are always trying to make changes/ | ||
| + | //Question? Please email [[mary@mcneel.com|Mary Ann Fugier]]Mary Ann Fugier, Rhino Technical Support, Seattle WA.// | ||
rhino/5/video/troubleshooting/slowrenderingmode.1643912599.txt.gz · Last modified: 2022/02/03 by maryfugier
