Re: Maya the server destroyer

> -Original Message- > > |> From: softimage-boun...@listproc.autodesk.com > > |> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf > > |> Of Morten Bartholdy > > |> Sent: Monday, May 23, 2016 10:43 AM > > |> To: Steve Parish; s

RE: Maya the server destroyer

> |> -Original Message- > |> From: softimage-boun...@listproc.autodesk.com > |> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf > |> Of Morten Bartholdy > |> Sent: Monday, May 23, 2016 10:43 AM > |> To: Steve Parish; softimage@listproc.auto

RE: Maya the server destroyer

Parish; softimage@listproc.autodesk.com |> Subject: Re: Maya the server destroyer |> |> Hmm - we don't really have any problems with Maya and RR |> even on large scenes. As Ed said, when simulating, cache |> locally and distribute the cache to render clients in a |> local temp fol

Re: Maya the server destroyer

Hmm - we don't really have any problems with Maya and RR even on large scenes. As Ed said, when simulating, cache locally and distribute the cache to render clients in a local temp folder - this lightens the network load quite a lot, and definately use tiled, mipmapped textures if your renderer

RE: Maya the server destroyer

The day has 24 hours, if that does not suffice, I will take the night _ From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Steve Parish Sent: Friday, May 20, 2016 7:17 PM To: softimage@listproc.autodesk.com Subject: Maya the server dest

Re: Maya the server destroyer

m >> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Ed Manning >> Sent: Friday, May 20, 2016 9:15 PM >> To: softimage@listproc.autodesk.com >> Subject: Re: Maya the server destroyer >> >> >> >> use the "render local" o

Re: Maya the server destroyer

*On Behalf Of *Ed Manning > *Sent:* Friday, May 20, 2016 10:13 PM > > *To:* softimage@listproc.autodesk.com > *Subject:* Re: Maya the server destroyer > > > > It's not Maya's fault. It's how the render manager, in this case Royal, > has its options set. > > > >

RE: Maya the server destroyer

-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Ed Manning Sent: Friday, May 20, 2016 10:13 PM To: softimage@listproc.autodesk.com Subject: Re: Maya the server destroyer It's not Maya's fault. It's how the render manager, in this case Royal, has its

Re: Maya the server destroyer

nt softimage batch > rendering actually is… > > > > > > *From:* softimage-boun...@listproc.autodesk.com [mailto: > softimage-boun...@listproc.autodesk.com] *On Behalf Of *Ed Manning > *Sent:* Friday, May 20, 2016 9:15 PM > *To:* softimage@listproc.autodesk.com

RE: Maya the server destroyer

Sent: Friday, May 20, 2016 9:15 PM To: softimage@listproc.autodesk.com Subject: Re: Maya the server destroyer * use the "render local" option, which writes the images to a temp directory on the render machines, then copies to the server. * set chunk size to a large number t

Re: Maya the server destroyer

check your logfiles to see where the biggest latencies are. On Fri, May 20, 2016 at 3:30 PM, Ed Manning wrote: > and stagger the start times -- Royal might have a built-in delay option > for this. that way the machines don't all hit the server at once for the > same files. >

Re: Maya the server destroyer

and stagger the start times -- Royal might have a built-in delay option for this. that way the machines don't all hit the server at once for the same files. On Fri, May 20, 2016 at 3:28 PM, Ed Manning wrote: > and if your renderer supports proxies (I think most of them

Re: Maya the server destroyer

and if your renderer supports proxies (I think most of them do), use them! On Fri, May 20, 2016 at 3:14 PM, Ed Manning wrote: > >- use the "render local" option, which writes the images to a temp >directory on the render machines, then copies to the server. >-

Re: Maya the server destroyer

- use the "render local" option, which writes the images to a temp directory on the render machines, then copies to the server. - set chunk size to a large number to minimize the number of times the scene has to be loaded by the network machines - turn off any unnecessary aovs -

Maya the server destroyer

My Maya misery continues.. We can't seem to be able to submit jobs without bringing the server to its knees. Anything with simulation or large scenes just jams everything up. I can only really submit to 3 machines. We're using Royal Render.. Any suggestions? Thanks Steve P -- Softimage