Comments on: Yadra - Yet Another Distributed Rendering App

By: Thomas

Thomas — Tue, 08 Jul 2008 17:26:38 +0000

Don't press ctrl+W here. haha

By: BlendMaster

BlendMaster — Fri, 06 Jun 2008 16:35:17 +0000

it ried DrQueue, farmerjoe, yadra, then blendermans render script, and a couple of others, including on from hazard but i have to say, i liuk this one the most so far, i guess its the interface or sumething, but its really easy to set up, adding slaves is a breeze, and i like that you can specify the ports and all that. so yeah, i liek it :)

By: birs93

birs93 — Mon, 02 Jun 2008 19:13:55 +0000

lol i tought it said disturbed XD

By: Oliver Schulze

Oliver Schulze — Tue, 05 Feb 2008 21:49:25 +0000

Hi,

a new version of yadra is available on http://blendoli.googlepages.com/yadra. Heres a list of changes:

- implemented multiple-jobs rendering
- added a new background image
- show up all active slaves (even if there are no jobs)
- added the possibility to remove inactive slaves from list
- reordered the done-list (newest on top)
- added multiple output-formats (png, jpeg, …)
- made the web-ui more flexible, now it is possible to put the templates in subdirectories
- added rendering time
- added pause for slaves (all the time, not only for one job)
- removed some bugs, regarding the rendering process/made the process more stable
- made it possible to render multiple jobs with the same name
- worked-over the code, switched to Subversion (on Sourceforge) and Eclipse
- fixed error, when master wanted to move the work folder, and the slaves wrote into it, that didn't work
- Fixed connect timeout error (could lead to a deadlock on the slaves): added timeout to socket connect
- Fixed problem of config (passphares was not recognized when creating a new slave)
- Fixed Problem, when setting the work directory to the same as the start directory (resulted in 0-Byte Filesin Web-Directory)

Have fun using it!

By: an8kid

an8kid — Sat, 02 Feb 2008 15:00:03 +0000

wow…
i just got round to trying this today….
its sooo slow… it was so much quicker rendering on my PC than on this render farm…

By: Reaction

Reaction — Sun, 20 Jan 2008 18:05:57 +0000

I create AVI Raw files ready for conversion to WMV. So all I need is a program on the master that can be given the relative speeds of each machine (including itself!); then calculate how many frames each machine should do; then send a simple command (over a network connection) to invoke identical Blender installations (with the necessary .blend files also local on each slave machine). When any machine finishes, it sends a message back to the master, which then tells that slave to copy its rendered AVI chunk back to a shared folder on the master.

If that's *not* what these render farm managers do, then I think it's time I learned Python or reawakened my Visual Basic skills!

By: Aussiedude

Aussiedude — Sun, 20 Jan 2008 03:57:16 +0000

I had a go at using the frameserver to setup a renderfarm of sorts when I was in high school last year. The computer lab I was in had 32 computers with this setup:
Processor: Intel Pentium 4 3.2GHz - Dual Core!
RAM: 2GB

With basically 64 processors around me I couldn't miss the chance to make a renderfarm. So I got my blend file, put it on the network. Opened the file on all computers and got the list of their IP's from my teacher. I wrote a C++ script that made a html file with a link to every frame in my animation with each computer rendering a near equal number of frames (about 250 frames so about 8 frames per computer). Then I used a download manager for firefox just to download all the links to frames in order with 32 frames downloading at a time. So that every computer was being used. Then I just downloaded all the frames to a laptop that was connected to the network.

It took a while to setup but it was worth it, worked like a charm when done. I probably did things the long way but I did so because:
1. I don't understand the so-called 'simple' renderfarm scripts and tools for blender
2. I didn't have the time nor the desire to write a script or tool myself that did all this automatically, I didn't think I would be doing it again either, so I just did it all manually.

By: lindamus

lindamus — Sat, 19 Jan 2008 10:45:54 +0000

Well,

this seems like a nice little project. Had a bit of a play with it all, but could not get the slaves to render output (from the looks of it).

Will keep my eye on it though, cause it does seem to be heading down the right track.

By: vidrazor

vidrazor — Sat, 19 Jan 2008 03:54:39 +0000

Pretty useless if all it can render to is jpeg.

By: Karl

Karl — Fri, 18 Jan 2008 21:56:25 +0000

@Reaction:
I can't speak for Yadra or FarmerJoe, but I would suggest a look at DrQueue - it works by sending one frame/bucket to each render slave, and then waits for a slave to finish. As soon as one slave finishes, the master sends it another bucket/frame to render. This way all machines pick up work as fast as they can, and your renderfarm is used to maximum efficiency. DrQueue also has also been used professionally and is production-proven. Comes thoroughly recommended :)

Karl