Ger wrote:

> clipka wrote:
> 
>> Am 20.01.2014 08:39, schrieb Ger:
>>> I had a render running that's pretty big (20GB mem use)
>>                                             ^^^^^^
>>> and it fails with a "Operation timed out" problem.
>> ...
>>> My guess is that pov times out waiting for the swap somehow.
>>                                   ^^^^^^^^^^^^^^^^^^^^
>> ...
>>> Running Povray 3.7 with the -CC switch on Opensuse 13.1 on a 16GB 8-core
>>                                                                ^^^^^^
>> Bad idea (thought not nearly as bad as on a Windows machine).
>> 
>> 
>>> Btw, I've had renders of similar size, and larger, running under Povray
>>> 3.6 And even though they chewed the heck outta the swap drive, they
>>> never timed out.
>>                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> As speed doesn't seem to be a matter for you, trying to lower the number
>> of competing threads using +WT4 or some such could be worth trying. With
>> the swap drive surely being the bottleneck, you might even consider
>> +WT1, reducing page thrashing to the absolute minimum possible in this
>> setup.
>> 
>> Note that the more worker threads you have, the less coherent
>> consecutive memory accesses will be.
> 
> Sounds logical. I'll give the +WT1 option a go and see what happens
> As a side note, when the actual render starts it never drops below 95% CPU
> usage until it finishes.
> 
No such luck

Render Time:
  Photon Time:      No photons
  Radiosity Time:   No radiosity
  Trace Time:       1 hours  5 minutes  6 seconds (3906.412 seconds)
              using 1 thread(s) with 3833.698 CPU-seconds total

Rendering frame 11 of 4091

Operation timed out.
Operation timed out.
Render failed

-- 

Ger

Post a reply to this message