[Sidefx-houdini-list] Mantra farm rendering to server killing network, ideas?
ron.schab at gmail.com
Mon Sep 8 04:52:08 EDT 2014
Hope things are well.
If I am not mistaken we had a similar issue at that place where they
emulated those freezing temperatures Mumble, Sven and all them had to face
for us artists at our desks despite the fact of us working in Sydney ;)
I can't quite remember the exact reason then nor the exact solution but we
- the volumetrics team - caused heavy filer loads with some renders/sims as
well and had to fix a similar issue. I believe it had more to do with
heavy read/write access rather then filesize. I THINK the solution was a
tick box on render submission telling the farm to write to the blade's
local storage first and then triggering a separate job to copy the finished
file over to its final destination afterwards. If you are in touch with
DanB he probably remembers more in depth. Also I think Matt Ebb would too
:). Good luck and have fun.
On Sep 8, 2014 9:46 AM, "Matt Estela" <matt.estela at gmail.com> wrote:
> Curious if anyone else has suffered this sort of thing;
> We sent a Mantra job to the farm, relatively fast per-frame times, but deep
> exr's with lots of layers meaning it came in at around 120mb per frame.
> When this was rendered by lots of farm machines at once (like 200 or more),
> this was enough to bring the filer to its knees, lots of fingers pointed,
> sad sysadmins.
> I know we've rendered stuff heavier than this before with PRman. Turns out
> this problem had been identified and fixed a while ago, in that our Maya
> PRman jobs automatically render to the local scratch disk locally per farm
> machine, then copy the frame to the filer when done, keeping the network
> Anyone implemented such a thing in Mantra? Or know of mystery Mantra
> options to force it to keep its network write operations to a minimum?
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list