This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| DrQueue | |
|---|---|
| Name | DrQueue |
| Developer | DreamWorks Animation, Blur Studio, Sony Pictures Imageworks |
| Initial release | 2000s |
| Programming language | Python (programming language), C (programming language), Qt (software) |
| Operating system | Linux, FreeBSD, macOS, Microsoft Windows |
| License | GNU General Public License |
DrQueue DrQueue is an open-source distributed render farm management and job queuing system used in computer animation, visual effects, and digital content creation pipelines. It coordinates rendering tasks across heterogeneous compute nodes and integrates with popular renderers, asset management systems, and production tools. The project was developed and matured through collaboration among studios and contributors in the film industry and open-source software community.
DrQueue provides centralized scheduling, job distribution, and monitoring for batch rendering and computational tasks in studios such as DreamWorks Animation, Pixar, Industrial Light & Magic, and Sony Pictures Imageworks. It targets environments using renderers like RenderMan, Arnold (renderer), Mental Ray, V-Ray, and Cycles (render engine), and integrates with compositing suites including Nuke (software), Adobe After Effects, and Fusion (software). Administrators use DrQueue alongside asset management solutions such as Shotgun (software), Perforce, Git (software), and Subversion to manage production data across clusters provisioned with systems like SLURM Workload Manager, Torque (software), and HTCondor.
DrQueue implements features for job queuing, frame-level task splitting, priority scheduling, resource locking, and failure recovery compatible with pipelines using Maya, Houdini, Blender, and 3ds Max. It offers a client/server architecture with a central scheduler, remote workers, and GUI tools for submission and monitoring that complement studio dashboards used at Walt Disney Animation Studios and Blue Sky Studios. The system supports dependency graphs, chunking, resubmission policies, and plugin hooks to interface with render farms managed by Autodesk, Foundry, and SideFX. Logging and auditing integrate with enterprise tools like Splunk, ELK Stack, and Nagios for operational visibility.
The core components include a master server, dispatcher, worker daemons, and submission clients similar to architectures found in Sun Grid Engine, LSF (software), and Microsoft HPC Pack. The master database backend may be implemented with SQLite, PostgreSQL, or MySQL, while interprocess communications rely on TCP/IP sockets and RPC patterns adopted in projects like Apache Thrift and gRPC. GUI clients built with Qt (software) and web frontends using Flask (web framework) or Django provide cross-platform control comparable to tools used by Weta Digital and Framestore. Integration adapters connect to renderers such as Mantra (renderer) and asset systems like Alienbrain.
Typical workflows begin with artists in Maya or Houdini submitting jobs through DrQueue clients or command-line tools, specifying frame ranges, renderer, and resource constraints. Jobs are scheduled across compute nodes running CentOS, Ubuntu, or Windows Server with GPU resources provisioned via NVIDIA drivers and orchestration by Kubernetes or bare-metal cluster managers. Monitoring and retry logic are visible in GUIs similar to those from Deadline (Thinkbox) and Qube! (pipeline), while custom scripts written in Python (programming language) or Perl automate dependency resolution, asset staging with rsync, and cache management using OpenCache patterns. Notification hooks can post updates to Slack, JIRA, and Confluence for production tracking.
DrQueue originated in the early 2000s as studios sought lightweight, scriptable render farm controllers alongside commercial packages like Autodesk Backburner and research systems such as Condor (software). Contributions came from engineers affiliated with DreamWorks Animation, Blur Studio, and independent open-source contributors, influenced by design decisions from Sun Microsystems cluster tools and the GNU Project. Over time, support for modern renderers, operating systems, and integration points with continuous integration servers like Jenkins and GitLab CI/CD evolved through community-driven patches, mailing lists, and repositories hosted on platforms pioneered by SourceForge and GitHub.
DrQueue has been adopted by boutique studios, academic research labs, and large visual effects houses for batch rendering, simulation job distribution, offline compositing, and scientific visualization tasks at institutions such as NASA, CERN, and university research groups. Use cases include feature animation rendering pipelines at Illumination (company), crowd simulation runs for Weta Digital-style projects, and large-scale scientific rendering for projects involving Blender Foundation collaborations. Its lightweight footprint made it attractive for studios migrating from on-premise clusters to hybrid cloud deployments on providers like Amazon Web Services, Google Cloud Platform, and Microsoft Azure.
DrQueue is distributed under the GNU General Public License and is available for download and contribution through community repositories and archives. Source code and binaries have historically been available via open-source hosting services and packaged for distributions such as Debian, Red Hat Enterprise Linux, and FreeBSD. Commercial studios often extend DrQueue with proprietary plugins and integrate it with enterprise asset management and render management solutions from vendors like Autodesk, The Foundry, and Thinkbox Software.
Category:Render management software