POV-Ray : Newsgroups : povray.windows : Massively delayed Stop Render : Re: Massively delayed Stop Render Server Time
1 Oct 2023 02:09:30 EDT (-0400)
  Re: Massively delayed Stop Render  
From: Bald Eagle
Date: 11 May 2016 21:00:01
Message: <web.5733d581403444595e7df57c0@news.povray.org>
"Thorsten Froehlich" <nomail@nomail> wrote:

> The solution is to have enough memory to hold everything in RAM as the effects
> will go away for the most part.

Indeed, adding another 4GB card gave the following:

Render Statistics
Image Resolution 10240 x 7680

Pixels:         78643200   Samples:               0   Smpls/Pxl: 0.00
Rays:           78643200   Saved:                 0   Max Level: 1/5

Ray->Shape Intersection          Tests       Succeeded  Percentage

Cone/Cylinder                  2906377         1227799     42.25
Sphere                          456980          212075     46.41
Bounding Box                1618119693       386343042     23.88

Shadow Ray Tests:            537601   Succeeded:                 18880
Shadow Cache Hits:            15221

Peak memory used:        1867010048 bytes

Render Time:
  Photon Time:      No photons
  Radiosity Time:   No radiosity
  Trace Time:       0 hours  0 minutes 18 seconds (18.858 seconds)
              using 4 thread(s) with 63.304 CPU-seconds total
POV-Ray finished
CPU time used: kernel 78.56 seconds, user 122.55 seconds, total 201.12 seconds.
Elapsed time 492.78 seconds.
Render averaged 159591.86 PPS (391033.08 PPS CPU time) over 78643200 pixels.

I could probably figure out a few tricks to trim down the render time for
something that is in essence a "line drawing".

I'm going to see if my system can accept 16GB, and see how things go from there.
  Eventually, I'm sure I'll see if I can find one of these juicy-sounding Xeos
chips and build a system around that with handfuls of memory cards...   :)
Alas, other more mundane things must be financed first.

Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.