THE RENDER DISPATCHER

• Provides fully integrated network rendering. 
• Monitor and control rendering jobs from your workstation.
• Easily scriptable for custom applications.

 
Put Alfred In Charge
 
Alfred is the ideal foreman for your renderfarm. Alfred is a task based processing system specifically designed to manage distributed rendering. It manages the render tasks of an entire studio efficiently, automatically and robustly. Alfred is tightly integrated with Studio, and supports a powerful scripting language that allows integration with distributed computing requirements at your site. An optional remote execution server, Alfserver, collaborates with Alfred for added scalability. Alfserver adds significant capabilities for launching and tracking remote commands – a big win for larger renderfarms. Trust Alfred to automate your Studio’s render pipeline.

Every frame of Finding Nemo was dispatched by Alfred.

 
Get the Fastest Rendering Possible
 
Alfred manages resources by working from a “white board” that you control. It identifies system resources including rendering machines, groups, and individual users, and specifies the times they’re available. It controls rendering servers from a shared pool as needed. If they’re all in use, it waits until an appropriate machine becomes available. Alfred simplifies system administration by using a pattern-matching scheme to make service requests, so specific host names are unnecessary. System administrators can “hot-swap” machines from the pool even as jobs are executing. Coupled with user-defined priorities and access times, this approach ensures the highest possible productivity. Alfred’s command language adds still more power. Use it to distribute the separable rendering components of a final frame (such as shadows or reflections) to remote network renderers in parallel. You’ll get the fastest single-frame rendering possible and take full advantage of the computing powers of your network.

 
Monitor and Control Your Render Jobs from Your Workstation
 
With Alfred, you control your own jobs directly from your individual machine, instead of via a central batch processor. So multiple jobs can be active at the same time throughout the network, making optimal use of network processors and disks, with user permissions guaranteed. This arrangement adds fault tolerance as well. Since it doesn’t do any job processing itself, Alfred imposes only a modest demand on your local CPU.

 
Use Alfred With Studio and Your Own Applications
 
Alfred ships with Studio, and is optimized to seamlessly manage the application of RenderMan assets to your Maya files. You can develop your own “Alfred savvy” applications, and even create distributed services for Alfred to manage. Alfred provides progress notification, remote message collection, and automatic restart of tasks that have stopped due to errors or even system crashes.

 
Alfred’s Tight Integration Gives You Fast, Flexible Rendering
 
Although Alfred’s components are general purpose, together they make networked rendering of RenderMan effects extremely efficient and easy to administer. Alfred consists of these independent parts:

• The Monitor: The Alfred Monitor lets you see and control the current state of the job queue. It has an HTTP interface, so you can monitor and direct your jobs using a web browser from anywhere on the network (even on the road, if you set up the appropriate security). In addition to the controls for individual users, Alfred includes a “wrangler” version of the Monitor that allows an Alfred superuser to control the jobs of several users.
   
  The Alfred Monitor
  Immediately access job health and status.
  Quickly reprioritize or delete jobs.
  
  
• The Dispatcher: The Alfred Dispatcher manages the job queue. It traverses the job worklist and executes individual tasks hierarchically, in succession or in parallel depending on their relative dependency. When a job requires a remote server, the Dispatcher negotiates with the Maitre d’.
  
  
• The Maitre d’: The Alfred Maitre d’ acts as the system’s resource arbitrator. It continuously monitors the master schedule, which lists the available network services, and determines which users have permission to use them.
  
  
• NIMBY (Not In My Back Yard): The Alfred NIMBY is a desktop utility that communicates with the Maitre d’ to ensure that work from remote sources doesn’t interfere with the work of interactive users. When these systems are idle, during screen saver mode for example, remote work can be accepted and processed.