 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I don't know if this is a bug, something that usually happens or a problem
with my settings. Last night, I set up a rendering in PoseRay with five DAZ
Millenium figures and a backdrop and set it to render with lights created
by the HDRI simulation in PoseRay.
As of this morning, when I left for work, it hadn't finished rendering.
That's not so much of an issue, as I had a high poly-count scene with lots
of lights and radiosity. However, my CPU history showed that Pov-ray (the
only application running) was only using between 2-10% of the CPU. Most of
the CPU cycles were going unused. In the bit I monitored, the CPU never hit
20% usage. My past renderings have left the CPU pegged at or near 100% for
the entire duration.
Is this a bug or is there something I can do to avoid this in the future?
I'm running the most recent Pov-Ray and Pose-ray on a brand new Dell laptop
with Windows XP (don't have the machine specs here at work).
Thanks
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
One word: Swapping.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm not normally a Windows user--I'm temporarily using the Windows machine
until I get a faster, more 3D-capable Mac--so I'm not sure how I might
reduce swapping. (I assume you mean running out of RAM and needing to swap
data in and out of VM). Should I have restarted before rendering to clear
up memory reserved by (closed) apps?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dizzy J <diz### [at] gmail com> wrote:
> I'm not normally a Windows user--I'm temporarily using the Windows machine
> until I get a faster, more 3D-capable Mac--so I'm not sure how I might
> reduce swapping. (I assume you mean running out of RAM and needing to swap
> data in and out of VM). Should I have restarted before rendering to clear
> up memory reserved by (closed) apps?
Inactive applications don't consume memory.
If POV-Ray was swapping it means that POV-Ray was taking more memory
than you have RAM. There are only two possible solutions to this: Either
reduce the size of your scene or buy more RAM...
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> reduce the size of your scene
For example, does your scene use large image maps, huge numbers of CSG
objects, heavy radiosity or photons? Depending on the cause it may be
possible to reduce the memory usage without reducing the quality of the
image.
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Slime who wrote:
>> reduce the size of your scene
>
>For example, does your scene use large image maps, huge numbers of CSG
>objects, heavy radiosity or photons? Depending on the cause it may be
>possible to reduce the memory usage without reducing the quality of the
>image.
It's more likely that the bulk of the memory is taken up with those five
DAZ Millenium figures. I use the reduced resolution DAZ figures and the
converted .inc files are about 15Mb each.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Williams nous apporta ses lumieres en ce 2005-10-08 03:57:
> Wasn't it Slime who wrote:
>
>>>reduce the size of your scene
>>
>>For example, does your scene use large image maps, huge numbers of CSG
>>objects, heavy radiosity or photons? Depending on the cause it may be
>>possible to reduce the memory usage without reducing the quality of the
>>image.
>
>
> It's more likely that the bulk of the memory is taken up with those five
> DAZ Millenium figures. I use the reduced resolution DAZ figures and the
> converted .inc files are about 15Mb each.
>
That's 75 Mb. Add the ram used by POV-Ray itself, the base scene file and any other
include. Add the
space used by all textures. Add your backdrop. Add the internal representation of
everything in the
scene... That can add up real fast. If you also use radiosity, add the radiosity data.
To check how much RAM you sue, hit Ctrl+Shift+Esc to summon the task manager and find
"pvengine.exe"
in the process tab. It's probably way larger than your installed memory.
--
Alain
-------------------------------------------------
Bad spellers of the world UNTIE!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
