Architectural Visualization: Cloud Rendering and Hardware

Architectural Visualization: Cloud Rendering or Purchasing Hardware:

If your firm has looked into investing in either cloud rendering or hardware then you may find this article interesting. Both the cloud and hardware are topics that are widely talked about in the creative realms for good reason. The following article is an overview on both the pros and the cons of hardware and cloud rendering. Meticulously analyzing the costs, and saving feasibilities from the minutia to the general overview. Hopefully aiding you in your research to conclusion to purchase the best suitable asset to broaden and further the success of your firm and fulfill your rendering needs.

Hardware – GPU’s, Processors and More

As intriguing as purchasing your own hardware infrastructure and having a personalized render farm with dedicated render nodes sounds there’s a few variables to consider beforehand. There’s a predominantly overlooked issue associated with investing in machinery. Being that once the hardware has been purchased a large amount of capital is both literally and figuratively intertwined in it more than it would seemingly appear. Though one may try and not think about it – realistically building a renderfarm can be expensive. You need network infrastructure, storage, security and IT personal.

A purchase of thousands of dollars into expanding or building a new render farm is only one facet of the revitalization of a rendering system. Even at the lower end of the spectrum with the cost for a renderblade from RenderStorm starting at $2,200. Utilizing the machinery to the utmost of its capacities to maximize production to have a positive return of investment is always primary goal. Nonetheless, if you purchased your hardware to cover peak rendering times you may also have times your hardware remains idle. Aside from the initial cost, your company must also hire qualified technical staff, to be on standby to manage and fix any error that may arise during the rendering process rapidly to minimize wasted minutes. Another entity that may additionally be idle could possibly be creative staffing such as visualization specialists.

Cloud Rendering

Cloud Rendering can be considered a solution if your rendering infrastructure is exhausted, you’re under a tight deadline or you arenot interested in the investment in building a render farm. Different to the hardware option is that initial inventory investment is significantly less compared to a render farms hardware’s capital cost. Conclusively deeming cloud rendering a suitable for short term needs and can save money. Bear in mind some firms may not need a huge render farm whereas others with a smaller rendering demand would do just as well by simply relying on cloud rendering as their primary source.

“Updates” are also to be taken into consideration when cloud rendering, software is perpetually changing. Technological advances occur monthly or annually or as the software deems necessary. In some instances softwares are even modified for bug fixes. Fortunately meaning some aren’t as highly invasive as others. In relation to that, software license renewals must be reinstated annually adding another expense. Electrical costs will also improve if utilizing cloud rendering, rather than having a render farm ceaselessly operating for hours on end. Considering that a mid- range desktop computer use on average 850 wph when rendering, multiplied by 24 that equals 20,400 watts daily the equivalent of 20.4 kWh for one single computer.

Annual cost per node for Architectural

Arnold: Cost Per Year= $1,500, Nodes=5
Cinema 4D: Per Year=$100, Nodes=1
Redshift: Per Year=$500 Nodes=1
Vray: Per Year=$350, Nodes=3
X-Particles: Per year=$490

Leave a Comment