Slashdot Mirror
Build Your Own Render Farm
Another installment of Tom's Hardware's how-to articles has a look at what it might take to build your own render farm. The article looks at everything from top-to-bottom roll-your-owns to buying things pre-built and the pricing insanity that goes along with it. "If you are working as a freelance artist in the above-mentioned media, toying with the idea, or doing so as a hobbyist, then building even a small farm will greatly increase your productivity compared to working on a single workstation. Studios can even use this piece as a reference for building new render farms, as we're going to address scaling, power, and cooling issues. If you're looking at buying a new machine and are thinking of spending big bucks to get a bleeding-edge system, you might want to step back and consider whether it would be more effective to buy the latest and greatest workstation or to spend less by investing in a few additional systems to be used as dedicated render nodes."
Build Your Own Annoyingly Segmented 10 Page Article!
How to Run Out of Practical DIY Ideas!
Host Your Own Ads for Under $1000!
Turn 50% of Your Site into Flash Ads in One Day!
How to Fake Content!
Embedding Popup Ads the Automated Way!
Going from Pioneer to Slowly Losing Relevance in 10 Easy Steps!
Earn Pennies a Day By Inconveniencing Your users!
R.I.P. Tom's Hardware.
My work here is dung.
... or to spend less by investing in a few additional systems to be used as dedicated render nodes.
Especially if you buy used systems. Computer hardware depreciates fast.
I hear non-factory farming also produces denser images that are more pleasing to the eye and have a higher contrast value. Besides, you'd be helping out the small rendering businesses by only selecting local renders.
Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
Keyboard dust is made of people!
Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
The article touches on general bits of info that might have been time consuming to find. I live in a small town where commercials for clients like the local chamber of commerce are often put together in iMovie, and delivered in a rush. Recently I was approached by a local art director and was asked about moving from 3D stills (which I do occasionally) to 3D animation to be composited into commercial work (probably for bigger clients than the chamber...). I've determined that I can afford about 2-3 minutes of render time per frame before deadlines really start to get pushed out. So rendering infrastructure is very important.
/. renderfarm pretty soon, and I'll be sending my receipts to CmdrTaco.
My studio is unique in that I work with open source software, Blender, Lux, etc. And my clients dig it because many of them are into sustainability and see my philosophy as being similar to theirs. I've looked at outsourcing the animation projects to commercial renderfarms, but when you start to "Better Know a Linux Network," you move beyond "get it done" and start to take interest in your own little LAN. Next to my video compositing and 3D graphics books I have a big ol' fat Pro Linux System Administration book, and it's handy, and I like it that way.
The article points out that I can save $140 per node by not needing to buy Windows XP Pro 64 bit edition. This is actually great for me since I typically use the money I save on software to buy more hardware.
BTW, what's up with Slashdot javascript? I'm going to have to build a freaking
Dear Slashdot Pimp,
I am a little confused as to your business plan. Why would you offer advice to slashdotters on getting laid on their own, when it would be far more profitable to ensure they need to visit your stable of hos to get laid?
Might I suggest you acquire the services of a business plan consultant to help you maximize your profits by leveraging the synergisms of your diverse talent pool? Careful attention to branding (perhaps literally) and marketing could help you achieve your quarterly and yearly targets for growth and margins.
Sincerely,
Slashdot Business Plan Consultant
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
Even a single render node dramatically increases productivity for me.
I'm doing TG2 skybox renders, something that easily takes 12 hours each, and often two, three, four times that. Having a few render nodes (two at the moment) means I can continue working while a few frames are already rendering. That means more of my time is spent productive and less is spent waiting.
My render nodes aren't even dedicated machines, just other machines I have around that are mostly idle.
Assorted stuff I do sometimes: Lemuria.org
My grandparents rendered on their small farm, but unfortunately I hate lye soap.
Free Martian Whores!
Is this astroturfing? Their website implies that they can streamline frame rendering down by several orders of magnitude, but there's no indication about how. Their FAQ is content-free, using buzzword-laden statements like " . . . gives non-linear access to lighting, ambient occlusion, materials . . . ." What is "non-linear" supposed to mean here?
There's always going to be a place for a render farm. Even if 3D modelers tomorrow can work in real time with settings that would take hours to render today, that'll just mean that the render farm will be running with even higher settings that might not exist today. At some point, we'll be able to run a render farm doing ray tracing with hundreds of reflections and get realistic skin pores and wood grain out of the technique, but the modeler is only going to be working with 20 or so.
Not a typewriter
A total of 10 copies of XP (for 10 nodes) may sound like a big expense, but it actually adds $140 per unit, pushing the cost of these machines to about $485 per unit for a dual-core node or $610 per unit for a quad-core configuration.
I think Tom should have rephrased that to put it into perspective: "Don't worry only 20% of the node cost is from Windows". I find it amazing that the most expensive component on the cheaper node is Windows XP and on the beefier node, it's nearly the same price as the CPU. It's even more baffling that this statement appears on the same page in reference to CPU selection:
It's really all about how much you want to spend here, because this is the single most expensive component required for each node.
Maybe Tom is a secret Linux fan and is hinting that Windows isn't a component but a tax. Or maybe he's just really bad at math.
This is where I got off. I wasn't aware that dual core processors treated ram separately. Thats news to me, and the guys at AMD, Intel, MS, and Linus as well. Every OS I'm aware of bases the memory available on the app, not the core, with most 32 bit OSes allowing for about 3G of memory usable to the app (roughly a gig is part of the kernel space for various things in most cases), and allowing for more with some kernel tuning depending on the OS. I think Linux allows for that, I know Windows and FreeBSD do.
I also guess he's never heard of PAE? Last I checked pretty much every modern processor and OS was capable of supporting 36 bit addressing, meaning a process is more than capable of addressing vastly larger amounts of RAM if its designed to do so, and even without support directly in the application, you can run multiple processes to get the 3G or so per process, which with 2 processes you are at 6. So if your shitting rendering app is 32 bit, not PAE aware, single threaded and you have more than 1 core than you can just pile on more processes with any modern OS and exceed 4G of usage. With a real rendering app, i.e. multithreaded, PAE aware and still 32 bit, its a no brainer. Of course if you're going through the effort to do all this, what are the chances your renderer is going to be 32 bit instead of 64? This is a question I really do not know as I'm not a render monkey, but I just can't see anything that matters still being a 32 bit app unless RAM really doesn't matter in rendering, which lets face it, for a complex scene, it does.
Its good to know Tom's has some real techs working for him that understand how computers work.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
And three months to finally get laid, and three hours of crying afterwords. Followed by three apologetic phone calls, three stalking incidents, three calls by her to the police, a restraining order keeping you three hundred feet from her at all times...
Help fight poverty: Punch a poor person.
It's called a botnet.
TYVM.
Any sufficiently advanced intelligence is indistinguishable from stupidity.
I did this two years ago with four cheap Dell Inspirons ($299 each, with free shipping). They're thin, easy to stack, and consume less power combined than my desktop. No discrete graphics, smallest possible HDD; all they need is processors (dual-core) and RAM. I run a stripped-down Ubuntu on them, and use some Python scripts to distribute Blender render jobs to them over the network, assembling the final frames on a file server.
Separate machines make an enormous difference. Even though rendering is relatively amenable to parallelization, a quad core machine isn't nearly as fast as two dual-core machines with the same specs. Even today, you would have to spend an awful lot of money to get a single machine that renders animations as fast as my two-year-old cluster of four.
I could even have built my own machines, and saved a few tens of dollars per machine, but the price was already pretty reasonable.