POV-Ray : Newsgroups : povray.pov4.discussion.general : Render to RAM / Ramdisk work driectory : Proof of concept : Re: Render to RAM / Ramdisk work driectory : Proof of concept Server Time
15 Jun 2024 10:33:36 EDT (-0400)
  Re: Render to RAM / Ramdisk work driectory : Proof of concept  
From: Alain
Date: 7 Apr 2017 17:10:23
Message: <58e8003f$1@news.povray.org>

> Hi all,
> Just to say that I am experimenting with rendering an animation using a RAMDISK
> (M$ iscsi virtual harddisk on 2012 R2 on RAM)
> Will export continuously the output to another HDD directory with robocopy.
> Thought that it would be a nice stepping stone for the implementation of bitcode
> rendering (don't remember if it is the official computing term of a differential
> re-parse)
> Will use a 43K (700 MB tga) for image_map and a max resolution output for file.
> The storage of the povstate in RAM should give the performance a big boost.
> Devteam, do you see any possible catches with that RAMdisk tech ?
> Will keep updated probably after 17 april.
> A+
> Rod.

The *.povstate file is only needed if you want to be able to stop, then 
resume, a render. In the latest beta, it's possible to disable it. The 
drawback is that an interupted render can't be resumed.

If you disable the continue feature by disabling the *.povstate file, 
the only write operation is that of the completed image as a .PNG file 
after the end of the render.

If you have enough RAM to prevent POV-Ray from needing to use the 
virtual memory, I don't think that using a RAM drive will have a large, 
or even significant, impact on the performance.

The presence of the RAM drive will reduce the available RAM. This may 
cause the internal storage to exceed the available RAM, forcing it to be 
stored on disk. In this case, the overhead of accessing your RAM disk 
can actually impair your performance and cause your render to take longer.

Post a reply to this message

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