Difference between revisions of "Documentation:Unix Section 8"
Jholsenback (talk | contribs) m (heading change) |
Jholsenback (talk | contribs) m (navigation) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
<!--</wikitalk>---> | <!--</wikitalk>---> | ||
==Speed Considerations== | ==Speed Considerations== | ||
| − | <p> | + | <p>The following tips can help you increase the speed at which your images render. Most of the time, the increase will be marginal, but in a very long render (some users have renders that take several days) even a small increase can save a noticable amount of time.</p> |
| − | The following tips can help you increase the speed at which your images render. Most of the | ||
| − | time, the increase will be marginal, but in a very long render (some users have renders that | ||
| − | take several days) even a small increase can save a noticable amount of time. | ||
| − | </p> | ||
===Render Priority=== | ===Render Priority=== | ||
| − | <p> | + | <p>The easiest way to change the priority across Unix systems is with the nice(1) command. The semantics vary from SVR4-based Unix to BSD-based Unix, so consult the manual page for instructions on usage.</p> |
| − | The easiest way to change the priority across Unix systems is with the nice(1) command. The | ||
| − | semantics vary from SVR4-based Unix to BSD-based Unix, so consult the manual page for | ||
| − | instructions on usage. | ||
| − | </p> | ||
===Render Window=== | ===Render Window=== | ||
| − | <p> | + | <p>Rendering without display will also speed up things. If your render is writing a lot of text to a terminal window, either hiding it, or better still, minimizing the window(s), will help somewhat. Note that the effect that these actions have is generally directly related to the time it takes to render the file, and the resolution of the render. They have less effect |
| − | Rendering without display will also speed up things. If your render is writing a lot of text | + | on long renders, and more effect on very fast renders.</p> |
| − | to a terminal window, either hiding it, or better still, minimizing the window(s), will help | ||
| − | somewhat. Note that the effect that these actions have is generally directly related to the | ||
| − | time it takes to render the file, and the resolution of the render. They have less effect | ||
| − | on long renders, and more effect on very fast renders. | ||
| − | </p> | ||
===Memory=== | ===Memory=== | ||
| − | <p> | + | <p>In general, the more memory you have (up to a point) the faster things will run, although this is not a direct effect, the less time Unix spends swapping things out to disk, the more time is available for your render.</p> |
| − | In general, the more memory you have (up to a point) the faster things will run, although this | ||
| − | is not a direct effect | ||
| − | time is available for your render | ||
| − | </p> | ||
===Scene Features=== | ===Scene Features=== | ||
| − | <p> | + | <p>Anti-aliasing, fog, halos, area lights, atmosphere ... all of these will cause your scene to require more time for completion. See the POV-Ray documentation for more details.</p> |
| − | Anti-aliasing, fog, halos, area lights, atmosphere | ||
| − | require more time for completion. See the POV-Ray documentation for more details. | ||
| − | </p> | ||
===Render Quality=== | ===Render Quality=== | ||
| − | <p> | + | <p>Consider using a lower <!--<linkto "Quality Settings">quality</linkto>--->[[Reference:Tracing Options#Quality Settings|quality]] setting if you're just testing your scene, and do not care about the quality of the output.</p> |
| − | Consider using a lower <!--<linkto "Quality Settings">quality</linkto>--->[[ | ||
| − | testing your scene, and do not care about the quality of the output. | ||
| − | </p> | ||
<!--<wikinav>---> | <!--<wikinav>---> | ||
<br> | <br> | ||
<table width=100% border=0 cellspacing=0 cellpadding=5> | <table width=100% border=0 cellspacing=0 cellpadding=5> | ||
<tr><td width=50% bgcolor=#EEEEEF> | <tr><td width=50% bgcolor=#EEEEEF> | ||
| − | [[Documentation:Unix Section 7#Bug Reporting via our | + | [[Documentation:Unix Section 7#Bug Reporting via our Bug Tracking System|Bug Reporting via our Bug Tracking System]]</td> |
<td width=50% bgcolor=#EEEEEF align=right> | <td width=50% bgcolor=#EEEEEF align=right> | ||
[[Documentation:Unix Table of Contents|Table of Contents]]</td></tr> | [[Documentation:Unix Table of Contents|Table of Contents]]</td></tr> | ||
Latest revision as of 13:30, 5 February 2013
|
This document is protected, so submissions, corrections and discussions should be held on this documents talk page. |
Speed Considerations
The following tips can help you increase the speed at which your images render. Most of the time, the increase will be marginal, but in a very long render (some users have renders that take several days) even a small increase can save a noticable amount of time.
Render Priority
The easiest way to change the priority across Unix systems is with the nice(1) command. The semantics vary from SVR4-based Unix to BSD-based Unix, so consult the manual page for instructions on usage.
Render Window
Rendering without display will also speed up things. If your render is writing a lot of text to a terminal window, either hiding it, or better still, minimizing the window(s), will help somewhat. Note that the effect that these actions have is generally directly related to the time it takes to render the file, and the resolution of the render. They have less effect on long renders, and more effect on very fast renders.
Memory
In general, the more memory you have (up to a point) the faster things will run, although this is not a direct effect, the less time Unix spends swapping things out to disk, the more time is available for your render.
Scene Features
Anti-aliasing, fog, halos, area lights, atmosphere ... all of these will cause your scene to require more time for completion. See the POV-Ray documentation for more details.
Render Quality
Consider using a lower quality setting if you're just testing your scene, and do not care about the quality of the output.
| Bug Reporting via our Bug Tracking System | Table of Contents |
|
This document is protected, so submissions, corrections and discussions should be held on this documents talk page. |