Page 2 of 2

Re: Remote pc as render slave?

Posted: Sun Jan 04, 2015 10:41 am
by glimpse
garytyler wrote:
glimpse wrote:Ise remote accessing software (VNC like) & setup something like DropBox - You can tweak the scene, (use all heavy materials & models already synchronised - placed on dropbox folder) & then only upload pretty light .OCS file (made on standalone or exported from Your app..) In this case You can fire up remote desktop once scene is done, fire the scene to render & keep working on other shot with Your computer. You basically split resources for two works. Not so elegant solution, but it might work bit better than using "network rendering".
Do you know if I could setup this same thing on an Amazon EC2 remote desktop, not the Octane AMI but just a regular EC2. Then, run multiple instances? Wish I knew why I can't find any information about this. I know this is what the Octane AMI is eventually supposed to do but I can't figure out what is stopping us all from doing it ourselves right now.
the thing that is stopping mainly would be kind a steep turning curve unless You're sort of developer (an already have some understanding how things work) & long technical guidelines doesn't bother You.

You can setup a "remote pc" in amazon, buy some instances on demand or spot instances (that would lover Your cost significantly) & with the help of third party software make this as a big render farm =) the problem here's is that OTOY seems to define in EULA that it doesn't allow running Octane Render on Virtual GPUs - so in theory, even if this is possible You're not allowed.

as mentioned You need quite a lot of knowledge how to do this - amazon provides a lot of guidelines, but for majority it's too complex & thus wide audience is waiting for one button solution.

OTOY is stepping into X.io (what I understand runs on their own servers) to provide better prices & higher flexibility. All this could movement is relatively new thing, especially with GPU computation & thus there's too much of unknown to be defined..-guess for developers it's hard to predict the exact outcome or give concrete timeline.

So, in the end You can start messing with complex stuff Yourself or..wait =)