Longest Hours..

[tolgahan]

There 's something wrong here...



I am still waiting..

[FrostKiwi]

7.5k x 4.2 k framebuffer with 48 BILLION polys is some major RAM nomming experience.

How is the Memory usage during render?

[tolgahan]

7.5k x 4.2 k framebuffer with 48 BILLION polys is some major RAM nomming experience.

How is the Memory usage during render?

[arqrenderz]

you have something like 27 Gb paginated to your HDD, you can wait a year more to render that image ..
There are various ways to reduce memory consumtion , just search them on the forum

[tolgahan]

you have something like 27 Gb paginated to your HDD, you can wait a year more to render that image ..
There are various ways to reduce memory consumtion , just search them on the forum

https://forum.corona-renderer.com/index.php/topic,12539.30.html

[FrostKiwi]

Ok, what happens here is classic performance loss by paging.

What happens, is that Windows creates a so called "pagefile", which off loads the memory from RAM to the Harddrive, one's it's full. It starts with Idle background processes and then goes to whatever it can offload.
Your Harddrive has only a fraction of the speed, especially in random read and writes, of RAM. Thus the CPU starves for data to crunch.
tl;dr: you are out of RAM
I presume your many Distributed systems as well.

You have commited 57gb and only avalible are 32gb, meaning you have to clear 25gb of Scene data to get the performance back to Optimal. (presuming all your render slaves have 32gb RAM aswell)
You can achieve this by making your foliage fade out by distance. I know some scatter programs have this, but you can even do this manually. Scatter only 50% foilage after 20 meters and only 10% after 50m.
Care with dispalcements! At such crazy crazy resolution the default 2px displacement subdivision calculation will produce a crap ton of geometry. This is the same as 1px displacement at half the resolution or 0.5px at quarter the resolution.
And as a last resort: Your Framebuffer will be massive, you can use Backburner's stripe render to let each machine only have a small framebuffer and combine the result at the end. This will make using the Framebuffers functions very difficult, but will distribute the RAM needed for the whole thing across multiple machines. So only as a last resort.

If you need a quick test: Disable foilage and diaplacements, now render should go fast. Or even white material override for even more free ram tests.

[rambambulli]

Good tip from SairesArt.

Maybe a long shot but do you use windows 10?

I had the same problem. When using the interactive render a lot my memory slowly increased after every render. The memory did not clean up.
In my case, this was a windows 10 problem. A driver leaked memory. The problem discovering this was that is wasn't a problem with every scene. Worse, it wasn't the same problem with the same scene every day.

[tolgahan]

yes very usefull tips.I use windows 7

I tried 7.5 k render when the render elements and displacement were off and it didnt cause any trouble.