Re: Maya the server destroyer

2016-05-24 Thread Steve Parish
Thanks for everyone's advice! Certainly a lot to play with to get things
cooking. We're using Arnold BTW.

On Tue, May 24, 2016 at 7:25 AM, Morten Bartholdy 
wrote:

> That would be really helpful Holger, and much appreciated :-)
>
> //Morten
>
>
>
> > Den 23. maj 2016 klokken 15:39 skrev Schoenberger :
> >
> >
> >
> > PS:
> > I am currently creating a small tool to test the network transfer speed
> from a fileserver to multiple machines at the same time for
> > our own investigation. I think I can release that to the public once it
> is finished (in a week?).
> >
> >
> >
> > Holger Schönberger
> > technical director
> > The day has 24 hours, if that does not suffice, I will take the night
> >
> >
> >
> >  |> -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.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 folder - this lightens the network load quite a
> >  |> lot, and definately use tiled, mipmapped textures if your
> >  |> renderer supports it. With Arnold this makes a huge difference.
> >  |>
> >  |> We actually only have problems which are more related to
> >  |> Vray being a memoryhog. Perhaps you have other bottleneck
> >  |> in your network?
> >  |>
> >  |> //Morten
> >  |>
> >  |>
> >  |>
> >  |> > Den 20. maj 2016 klokken 19:16 skrev Steve Parish
> >  |> :
> >  |> >
> >  |> >
> >  |> > 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.
> >
> >
> > --
> > 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.
>
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

RE: Maya the server destroyer

2016-05-24 Thread Morten Bartholdy
That would be really helpful Holger, and much appreciated :-)

//Morten



> Den 23. maj 2016 klokken 15:39 skrev Schoenberger :
> 
> 
> 
> PS:
> I am currently creating a small tool to test the network transfer speed from 
> a fileserver to multiple machines at the same time for
> our own investigation. I think I can release that to the public once it is 
> finished (in a week?).
> 
> 
> 
> Holger Schönberger
> technical director
> The day has 24 hours, if that does not suffice, I will take the night
> 
> 
> 
>  |> -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.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 folder - this lightens the network load quite a
>  |> lot, and definately use tiled, mipmapped textures if your
>  |> renderer supports it. With Arnold this makes a huge difference.
>  |>
>  |> We actually only have problems which are more related to
>  |> Vray being a memoryhog. Perhaps you have other bottleneck
>  |> in your network?
>  |>
>  |> //Morten
>  |>
>  |>
>  |>
>  |> > Den 20. maj 2016 klokken 19:16 skrev Steve Parish
>  |> :
>  |> >
>  |> >
>  |> > 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.
> 
> 
> --
> 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.

RE: Maya the server destroyer

2016-05-23 Thread Schoenberger

PS:
I am currently creating a small tool to test the network transfer speed from a 
fileserver to multiple machines at the same time for
our own investigation. I think I can release that to the public once it is 
finished (in a week?).



Holger Schönberger
technical director
The day has 24 hours, if that does not suffice, I will take the night



 |> -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.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 folder - this lightens the network load quite a
 |> lot, and definately use tiled, mipmapped textures if your
 |> renderer supports it. With Arnold this makes a huge difference.
 |>
 |> We actually only have problems which are more related to
 |> Vray being a memoryhog. Perhaps you have other bottleneck
 |> in your network?
 |>
 |> //Morten
 |>
 |>
 |>
 |> > Den 20. maj 2016 klokken 19:16 skrev Steve Parish
 |> :
 |> >
 |> >
 |> > 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.


--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: Maya the server destroyer

2016-05-23 Thread Morten Bartholdy
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 supports it. With 
Arnold this makes a huge difference.

We actually only have problems which are more related to Vray being a 
memoryhog. Perhaps you have other bottleneck in your network?

//Morten



> Den 20. maj 2016 klokken 19:16 skrev Steve Parish :
> 
> 
> 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.


RE: Maya the server destroyer

2016-05-21 Thread Schoenberger
Hi
 
Scenes:
- Yes, Softimage is the only application that supports multi-machine skip 
frames.  RR has a workaround for some render apps, you
have to enable "Keep scene open". 
 
- Enable "local scene copy". This copies the scene file once to the client. You 
might get issues if xgen files, textures or cache
files are set with an relative path to the scene file. 
RR has a copy delay for scene files, you can change this is in the config of 
each client. It simply slows down the copy process.
 
 
 
Textures:
- Local Textures:  Save .ma files. They are larger, but only copied once as you 
need to enable  "local scene copy". Use the Local
Texture submit in Maya. The texture files are copied once (with the same delay 
as the scene copy) to the client, the scene file is
copied and the texture paths in the scene file are changed to the local paths. 
As one texture is used for many layers, many scenes
and many scene versions during a project, you save a lot of traffic.
 
- If you have used Softimage with MRay, then Softimage was able to keep the 
texture files in memory. With Maya, the renderer has to
load the texture files when the frame render starts.
 
- Texture format: Which format do you use for your texture? If you do not need 
alpha or 16bit, then save jpegs with 90% quality, in
almost all cases you can not even get artifacts on the final image with "I want 
to have jpeg artifacts" contrast filters.
 
- Reduce the texture size: If the textures are painted, then you can reduce the 
size to 50-75% without any differrence in the final
image.
Just test it, render one frame, use a photoshop script to create 50% resultion 
textures, render the same frame. Compare the frames.
If you see differences, change these textures (not all) with a 75% resolution 
texture and render again.
 
 
Output:
- Local render out saves constant traffic as well. RR copies the whole frame at 
once instead of saving it constantly (depends on the
renderer as well)
 
- If you render .exr files, then enable "Crop EXR". The files will be smaller, 
therefore less traffic. You have to use Adobe CC
2014+ or Nuke. A hint for comp: If you use Nuke 8+ and you render one file with 
many AOV, then enable EXR 2.0 in rrConfig, tab misc.
Saves you traffic during comp.
 
 
 
 
Which renderer do you use?
 
 
Holger Schönberger
technical director
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 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 Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: Maya the server destroyer

2016-05-20 Thread Softimage
Hi,
RoyalRender now has a "keep open" option for the scene you send it, so even if 
you are sending it one frame at a time rather than a bunch it should wait until 
you explicitly send it another scene before flushing the current one!

Cheers 

Lawrence 

> On 20 May 2016, at 21:13, Ed Manning  wrote:
> 
> It's not Maya's fault. It's how the render manager, in this case Royal, has 
> its options set.
> 
> There is something bad about Maya and certain read/write operations over 
> network, but I don't think this is that.
> 
> Unless you're trying to render on Windows render nodes to a Linux or OS X 
> server running a bad SMB stack.
> 
> In which case you might as well be in the Sarlacc Pit.
> 
> 
> 
>> On Fri, May 20, 2016 at 3:46 PM, Sven Constable  
>> wrote:
>> Maya also loads the scene at every frame? I was thinking only 3dsmax had 
>> this awful behavior. If they would know how elegant 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
>> 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 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  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.
> 
> --
> 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.

Re: Maya the server destroyer

2016-05-20 Thread Steve Parish
Thanks for the help guys, I'll take a close look at everything! Enjoy your
weekend :)

On Fri, May 20, 2016 at 4:40 PM, Sven Constable 
wrote:

> Yeah, I know. But the feature itself, to use chunks of frames was
> originally developed by Holger to circumvent the issue by the
> renderer/batch executable loading the scene at every frame, wasn't it? Like
> the KSO (keep scene open) feature in RR, also adressing this problem.
>
>
>
> *From:* softimage-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 options set.
>
>
>
> There is something bad about Maya and certain read/write operations over
> network, but I don't think this is that.
>
>
>
> Unless you're trying to render on Windows render nodes to a Linux or OS X
> server running a bad SMB stack.
>
>
>
> In which case you might as well be in the Sarlacc Pit.
>
>
>
>
>
>
>
> On Fri, May 20, 2016 at 3:46 PM, Sven Constable 
> wrote:
>
> Maya also loads the scene at every frame? I was thinking only 3dsmax had
> this awful behavior. If they would know how elegant 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
> *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 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 
> 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.
>
>
>
> --
> 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.

RE: Maya the server destroyer

2016-05-20 Thread Sven Constable
Yeah, I know. But the feature itself, to use chunks of frames was originally 
developed by Holger to circumvent the issue by the renderer/batch executable 
loading the scene at every frame, wasn't it? Like the KSO (keep scene open) 
feature in RR, also adressing this problem.

 

From: softimage-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 
options set.

 

There is something bad about Maya and certain read/write operations over 
network, but I don't think this is that.

 

Unless you're trying to render on Windows render nodes to a Linux or OS X 
server running a bad SMB stack.

 

In which case you might as well be in the Sarlacc Pit.

 

 

 

On Fri, May 20, 2016 at 3:46 PM, Sven Constable  
wrote:

Maya also loads the scene at every frame? I was thinking only 3dsmax had this 
awful behavior. If they would know how elegant 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
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 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  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.

 

--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

Re: Maya the server destroyer

2016-05-20 Thread Ed Manning
It's not Maya's fault. It's how the render manager, in this case Royal, has
its options set.

There is something bad about Maya and certain read/write operations over
network, but I don't think this is that.

Unless you're trying to render on Windows render nodes to a Linux or OS X
server running a bad SMB stack.

In which case you might as well be in the Sarlacc Pit.



On Fri, May 20, 2016 at 3:46 PM, Sven Constable 
wrote:

> Maya also loads the scene at every frame? I was thinking only 3dsmax had
> this awful behavior. If they would know how elegant 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
> *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 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 
> 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.
>
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with 
"unsubscribe" in the subject, and reply to confirm.

RE: Maya the server destroyer

2016-05-20 Thread Sven Constable
Maya also loads the scene at every frame? I was thinking only 3dsmax had this 
awful behavior. If they would know how elegant 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
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 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  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.

Re: Maya the server destroyer

2016-05-20 Thread Ed Manning
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.
>
>
>
> On Fri, May 20, 2016 at 3:28 PM, Ed Manning  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  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 
>>> 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.

Re: Maya the server destroyer

2016-05-20 Thread Ed Manning
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 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.
>>- 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 
>> 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.

Re: Maya the server destroyer

2016-05-20 Thread Ed Manning
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.
>- 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 
> 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.

Re: Maya the server destroyer

2016-05-20 Thread Ed Manning
   - 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  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.

Maya the server destroyer

2016-05-20 Thread Steve Parish
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.