You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.161.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 10:07, 1 October 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.161.166.4. The blocked range is 54.161.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Short description|Computer system for rendering computer-generated imagery))
((multiple issues|
((disputed|date=February 2012))
((more citations needed|date=May 2016))
))

[[File:Render farm (2825013521).jpg|thumb|150px|Render farm in [[Madrid]], 2008]]
A '''render farm''' is a high-performance computer system, e.g. a [[computer cluster]], built to [[Rendering (computer graphics)|render]] [[computer-generated imagery]] (CGI), typically for film and television [[visual effects]].

A render farm is different from a '''render wall''', which is a networked, tiled display used for [[real-time rendering]].<ref>((cite web| url = http://www.doubletongued.org/index.php/dictionary/renderwall| title = "renderwall" definition from Double-Tongued Dictionary<!-- Bot generated title -->| date = 28 October 2004))</ref> The rendering of images is a highly [[Parallel computing|parallelizable]] activity, as frames and sometimes [[Tiled rendering|tiles]] can be calculated independently of the others, with the main communication between [[central processing unit|processors]] being the upload of the initial source material, such as models and textures, and the download of the finished images.

==Render capacity==
Over the decades, advances in computer capability have allowed an image to take less time to render. However, the increased computation is appropriated to meet demands to achieve state-of-the-art image quality. While simple images can be produced rapidly, more realistic and complicated higher-resolution images can now be produced in more reasonable amounts of time. The time spent producing images can be limited by production time-lines and deadlines, and the desire to create high-quality work drives the need for increased computing power, rather than simply wanting the same images created faster.  Project such as the [[Big and Ugly Rendering Project]] have been available for rendering images using [[Blender (software)|Blender]] across both widely distributed networks and local networks.<ref name="bebl">((cite book |title=Beginning Blender: Open Source 3D Modeling, Animation, and Game Design |last=Flavell |first=Lance |year=2011 |publisher=Apress |isbn=9781430231271 |page=374 |url=https://play.google.com/store/books/details?id=aHmlWV50mIAC |access-date=24 September 2017))</ref>

==Management==
To manage large farms, a ''[[Queue management system|queue manager]]'' is required that automatically distributes processes to the many processors. Each "process" could be the rendering of one full image, a few images, or even a [[Tiled rendering|sub-section (or ''tile'')]] of an image. The software is typically a [[client–server]] package that facilitates communication between the processors and the queue manager, although some queues have no central manager. Some common features of queue managers are: re-prioritization of the queue, management of software licenses, and algorithms to best optimize [[throughput]] based on various types of [[Computer hardware|hardware]] in the farm. Software licensing handled by a queue manager might involve dynamic allocation of licenses to available CPUs or even cores within CPUs.
A [[tongue-in-cheek]] job title for systems engineers who work primarily in the maintenance and monitoring of a render farm is a ''render [[Wrangler (profession)|wrangler]]'' to further the "farm" theme. This job title can be seen in film credits.

Beyond on-site render farms, cloud-based render farm options have been facilitated by the rise of [[high-speed Internet]] access. Many cloud computing services, including some dedicated to rendering, offer to render farm services that bill only for processor time used. Understanding the cost or processing time required to complete rendering is unpredictable so render farms bills using GHz per hour. Those considering outsourcing their renders to a farm or to the cloud can do a number of things to improve their predictions and reduce their costs.<ref>((Cite news|url=https://garagefarm.net/blog/show-me-the-money-how-pricing-works-in-a-render-farm|title=How render farm pricing actually works|date=2021-10-24|work=GarageFarm|access-date=2021-10-24|language=en-US))</ref><ref>((cite web |title=How Blender Render Farms Save Time and Money |url=https://rentaflop.com/blog/how-blender-render-farms-save-time-and-money |website=rentaflop |access-date=31 May 2023))</ref> These services eliminate the need for a customer to build and maintain their own rendering solution. Another phenomenon is collaborative rendering, in which users join a network of animators who contribute their processing power to the group. However, this has technological and security limitations. Some cloud rendering farms have been developed over a long period of time and are TPN certified, which is a relatively authoritative certification in terms of security performance. <ref>((Cite news|url=https://www.ttpn.org//|title=TPN Homepage|language=en-US))</ref>

==See also==

* [[Parallel rendering]]
* [[Queueing theory|Queue]]
* [[Server farm]]

==References==
((Reflist))

((DEFAULTSORT:Render Farm))
[[Category:3D rendering]]
[[Category:Graphics hardware]]
[[Category:Applications of distributed computing]]

Pages transcluded onto the current version of this page (help):

Render farm (edit)
Template:Ambox (view source) (template editor protected)
Template:Cite book (view source) (protected)
Template:Cite news (view source) (protected)
Template:Cite web (view source) (protected)
Template:Disputed (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Disambiguation (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Redirect (view source) (protected)
Module:SDcat (view source) (template editor protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Render farm.

Retrieved from "https://en.wikipedia.org/wiki/Render_farm"