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 <etmth...@gmail.com> wrote: > 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 <etmth...@gmail.com> wrote: > >> >> - 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 >> - try to set up local simulation caches on the render machines >> - don't know what renderer you're using, but most can save you a lot >> of disk read if you convert all textures to tiled mipmapped versions >> - for that matter, you might want to set up local texture caches too. >> >> >> >> >> On Fri, May 20, 2016 at 1:16 PM, Steve Parish <porkypar...@gmail.com> >> wrote: >> >>> 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 Mailing List. >>> To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com >>> with "unsubscribe" in the subject, and reply to confirm. >>> >> >> >
------ Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
