Out of core Tweet

[BorisGoreta]

I am getting message Out-of-core memory limit exceeded on my nodes while the master computer is rendering the scene normaly. All machines have 6GB GPUs.

Here is how I set up nodes to use out of core:

octane_slave.exe --net-master-address 192.168.200.20 --net-master-port 21000 --out-of-core "6g"

What am I doing wrong ?

Master computer says Out-of-core RAM (used/max): 1423/6144 MB so the scene does not use all 6GB of RAM. Why does it always report it is out of RAM ?
Nodes have enough system RAM.

[BorisGoreta]

I have some further insights.

One node which has all 6Gb cards fails completely and halts the render progress, if I kill the slave the render continues.

Other node which has 2 6GB cards and 3 8GB cards actually renders but only with 8GB cards. 6GB cards don't render ( fans not spinning )


Is out of core on nodes working for anyone ?

[Seekerfinder]

Hi Boris,
I see you got no responses here... We plan to build a render slave and I have the same question. And another - I'll post under seperate thread but perhaps you have some insight as well since you've played with render slaves(?).

Does Octane use / need system RAM (not GPU ram) on slave machines?

Cheers,
Seeker

[BorisGoreta]

You need RAM on the slaves. For the 4233 MB GPU RAM scene you need 5300 MB system RAM on the slaves. I guess 16GB system RAM is recommended so you could use 12GB card to its full RAM potential.

CPU usage on the slaves went from 2 % to 35 % during rendering. It started at 2% and then gradually climbed to around 35% in a period of 2 minutes and then stayed there until the rendering was finished.

Initially I had shitty Celerons inside slaves since i thought this was a GPU renderer but then swapped them with i7-4760 @ 3.6 GHz because of heavy CPU usage.

Celerons were climbing to 70% or even more.

This CPU usage is not consistent, sometimes slave CPUs stay below 7% but you can see from the screenshot they can be high too, this is not clear to me.

[BorisGoreta]

About that out of core on nodes problem I solved it when a developer said that the out of core memory amount should be entered in bytes, not Gbytes.
When you used slave deamon to create the BAT file which starts the slave you could enter how many Gbytes you wanted assigned to out of core and it would creat the BAT file with Gbyte values which then wasn't working.
I am not sure if this fixed with the latest versions.
Anyway this is how it needs to look for 6GB out of core:

octane_slave.exe --net-master-address 192.168.178.20 --net-master-port 21000 --out-of-core 6442450944

And then out of core works on the slaves.