Dataclay’s documentation does not name one single factor that limits throughput when you scale Templater across several render nodes, and it does not give measured throughput numbers. What it does give is a set of documented settings and limits that each affect how a batch spreads across machines: how many Bots read one data source, how often a Bot checks for new data, how many jobs a Bot can queue, how QUE assigns jobs to satellites, how licenses and credits are counted, and how After Effects is set up on each machine. This page walks through those one at a time so you can check each one against your own setup. Which of them is the biggest limit for your project is not stated here, and the way to find out is a test run on your own machines.
How Templater Spreads Work Across Machines
Templater can break a massive workload into batches queued sequentially, or run on multiple Bot machines in parallel. Those are the two shapes of scaling the documentation describes. Sequential batches keep the work on one machine and feed it in pieces. Parallel Bot machines split the work between computers.
The Bot is the part of Templater that does the unattended work. The Bot ships with the Templater Bot edition and works as a background process that watches for data and renders video. When you enable The Bot, Templater enters a server mode and checks your data source at regular intervals. For each queued row, The Bot sets render-status to processing, and then to done when output is finished. Using multiple Templater Bots on the same data source lets you process video faster, and the documentation names the setup steps for it.
To process one data source with several Bots, you must include a bot column or JSON key. Give each Bot a unique name in the Bot Name field under Bot Settings in Templater Preferences, and the bot column value assigns a row to the Bot with the matching Bot Name. A Bot Name is needed only when more than one Bot uses the same data source. The documentation notes that a Bot error code of 3, a ScriptError, can occur if a Bot Name is set but the data source has no bot column.
Before You Scale
Things to check on each render node
- Add a bot column and unique Bot Name for each Bot on a shared data source
- Confirm each Bot can queue up to a max of 20 jobs at any given time
- Manually assign QUE jobs to each satellite, QUE does not load balance
- Deploy the Autograf, fonts, and effects to every QUE Satellite
- Verify licenses and credits: registration required for each machine, credits consumed per output
- Disable After Effects disk caching on any machine where Templater Bot is left enabled
With one Templater Bot, you or your app should only enter ready in render-status or empty the cell. That rule is one reason to design the data source around the number of Bots from the start. For a broader look at planning capacity, see the guide on sizing a render farm for unpredictable volume.
Multi-Bot Setup
How to run several Bots on one data source
-
Add a bot columnInclude a bot column or JSON key in your data source.
-
Name each BotGive each Bot a unique name in the Bot Name field under Bot Settings in Templater Preferences.
-
Assign rowsThe bot column value assigns a row to the Bot with the matching Bot Name.
-
Set render-statusWith one Templater Bot, you or your app should only enter ready in render-status or empty the cell.
-
Test the setupCheck them in that order on a small multi-machine test of your own.
Limits on the Bot Itself
A few documented limits apply to each Bot, and they matter once you add machines.
- A Templater error message states that Templater Bot can queue a max of 20 jobs at any given time.
- Templater Bot’s default polling interval for new data is 0.5 minutes, or 30 seconds.
- The minimum polling frequency is 0.3 minutes (18 seconds) for Google Sheets and 0.2 minutes (12 seconds) for JSON sources and URL feeds.
- Templater uses the Google Sheets API to read and write spreadsheet data and must regard API rate limits.
Read together, these give you the cadence of the system. When you enable The Bot, Templater checks your data source at regular intervals. It checks at an interval, and the shortest interval depends on the kind of data source. The documentation also says more than one Bot can read new data from the same Google Sheets spreadsheet, even from separate locations. If your batch comes from a spreadsheet, the data source itself is one of the things to check when you add nodes.
The Bot can also be driven without a spreadsheet. Templater Bot can be fed data through a command line interface to create new renders, and The Bot provides a command line interface. Since Templater 3.0, The Bot supports QUE, Google Sheets, URL feeds, and local JSON and TSV files as data sources. The guide on configuring the Templater Bot covers the settings in more detail.
Data Source Limits
Minimum polling interval by data source type
| Data source | Minimum polling interval | Supported since |
|---|---|---|
| Google Sheets | 0.3 minutes (18 seconds) | Before Templater 3.0 |
| JSON files / URL feeds | 0.2 minutes (12 seconds) | Since Templater 3.0 |
| Local TSV files | 0.2 minutes (12 seconds) | Since Templater 3.0 |
QUE Satellites and Job Assignment
QUE is Dataclay’s render queue and API for sending jobs to satellite machines running Templater. A QUE satellite is a unique machine running Adobe After Effects that requests data from QUE via Templater. QUE Satellites are authorized machines that process Jobs into output files, and each QUE Satellite is associated with the machine that added it to QUE. Templater adds the host machine as a QUE Satellite when you click Add to QUE.
The documentation is direct about how jobs reach those machines. QUE does not offer load balancing of jobs between satellites, but jobs can be manually assigned to satellites. When no satellite is specified, a new QUE job goes to the campaign’s default satellite. In the New Job dialog, Autograf, Job Status and Satellite are required fields. In QUE Batch Import you choose a Satellite and an Autograf from dropdowns, then click Upload. A job with render-status queued is waiting in line for an assigned satellite machine.
That has a plain consequence for scaling. If you add satellites but leave every job pointed at the default satellite, the jobs still go to that one machine, because QUE does not balance them for you. A satellite’s Processing Scope is either Single Campaign or All Campaigns, which is another setting to check when you add a machine.
Each satellite also has to be able to do the work. To render a QUE Job, the Satellite must have the Job’s Autograf and its fonts and effects installed. QUE does not copy Autografs to Satellites, so fonts, effects and project files must be deployed to each Satellite. A QUE Satellite must have the Autograf’s authoring application, such as After Effects, and Templater installed. QUE Satellite host info includes name, user, external and internal IP, OS, RAM, CPU, drive capacity and fonts, which lets you compare machines. The guide on what happens when a Templater batch fails mid-queue is a useful companion for planning around a machine that drops out.
Licenses, Seats and Credits
Every machine that runs Templater needs a way to be licensed, and the license type shapes how you can add nodes. Templater registration is required for each machine that hosts a Templater installation. Templater has two license key types, Standard (node locked) and Floating, set at the time of purchase, and the two keys each match a different build and are not interchangeable.
With a Standard license, activations are tied to the specific machine where they are activated. A Templater Standard License is activated on one machine at a time and must be deactivated to move it. With a Floating license, each key has one or more activations, also called seats. A floating key needs as many activations as the most people active at once. More machines can have the Templater floating build installed than the key has activations, and floating client machines point at the licensing server and check out a seat when one is released. With a floating license, the license returns to the pool when After Effects quits. Floating keys activate the Dataclay License Manager (DataclayLM) server, not Templater directly. The guide on what a floating license is for After Effects automation software explains the model.
Cloud machines have a note of their own. Templater can run on Windows Server machines in a cloud such as Amazon Web Services with no special Dataclay license, and running Templater in the cloud needs an appropriate After Effects license from Adobe. With a node locked Templater license, each VM reboot or new VM needs manual deactivation and reactivation. That detail is easy to overlook when machines are started and stopped often.
License Types
Standard vs. Floating license for render nodes
- How is it activated?
- Standard (node locked)Activated on one machine at a time
- FloatingEach key has one or more activations, also called seats
- Can you move it?
- Standard (node locked)Must be deactivated to move it
- FloatingReturns to the pool when After Effects quits
- Cloud VMs?
- Standard (node locked)Each VM reboot or new VM needs manual deactivation and reactivation
- FloatingMore machines can have the floating build installed than the key has activations
Templater has two license key types, Standard (node locked) and Floating, set at the time of purchase, and the two keys each match a different build and are not interchangeable.
Credits are the other count to track. With QUE Meter, each customized output consumes one credit, and outputs include spot checks, replicas, and renders. When the QUE Meter reaches zero, Templater’s status area shows an error that QUE credits are depleted, and Templater Bot stops and is auto disabled when QUE Credits run out. It can be enabled after a refill. Any active Templater license key (Rig, Pro, or Bot) can connect to QUE Meter and draw from a shared pool of credits, and credits are assigned to the organization the user belongs to, so a team can share them. Powered by QUE Meter, Templater must always have an internet connection to track credit usage. If your machines run overnight, check the balance before they start. The guide on the QUE Meter covers the feature.
Setting Up Each Machine
The last group of limits is about the machine itself. Leaving Templater Bot enabled for long periods can slow versioning because of After Effects layer caching. Dataclay recommends disabling After Effects disk caching on any machine where Templater Bot is left enabled. Since After Effects 24.3, Templater’s Purge all memory caches after each job no longer empties the disk cache, and the disk cache can be emptied under Edit, Preferences, Media and Disk Cache by clicking Empty Cache.
If you render through Adobe Media Encoder, the setup has its own steps. To have The Bot render with Media Encoder, check Replicate in Bot Settings and add a Media Encoder watch folder set to the Templater output folder. A Media Encoder machine rendering Templater replicas needs the same drive mappings and fonts as the creating machine. Dataclay warns that a cloud sync folder for Templater output can cause Media Encoder errors, so use a local or network folder. When Templater sends comps to Adobe Media Encoder, shell scripts run after versioning in After Effects, not after Media Encoder finishes.
Output settings matter on every node. A QUE Satellite’s Output Root matches the Destination field under Output Options in Templater’s main panel, and its Footage Root matches the Footage field under Batch Assets. The Templater Bot will overwrite existing files if it renders to the same output file name, so unique names help when several machines write to the same place. QUE Satellite Output Naming options are Unique, Prepend and Override, and with Unique the Satellite names output with the Job’s inherent _id. The guide on optimizing After Effects for the Templater Bot goes deeper on machine setup.
Bottom Line
The documentation does not say which single factor limits throughput when you scale across render nodes, so that part of the question stays open. It does state the pieces that decide how well a batch spreads: multiple Bots need a bot column and unique names, each Bot can queue a max of 20 jobs, polling has minimum intervals and Google Sheets API limits apply, QUE does not load balance between satellites, each satellite needs the Autograf, fonts and effects, licenses and credits are counted per seat and per output, and After Effects caching and Media Encoder setup affect each machine. Check them in that order on a small multi-machine test of your own. Start with Templater for Adobe After Effects for the product overview.
Frequently Asked Questions
What actually limits throughput when you scale Templater across multiple render nodes?
Dataclay’s documentation does not name a single limiting factor or give measured throughput numbers. It documents several limits that each affect scaling: a Bot can queue a max of 20 jobs, Bots poll at set intervals, QUE does not load balance jobs between satellites, and licenses and credits are counted per seat and per output. Test your own setup to see which one you reach first.
Can several Bots work on one data source?
Yes. Using multiple Templater Bots on the same data source lets you process video faster. You must include a bot column or JSON key and give each Bot a unique name in the Bot Name field.
Does QUE balance jobs across satellites?
No. QUE does not offer load balancing of jobs between satellites, but jobs can be manually assigned to satellites. When no satellite is specified, a new job goes to the campaign’s default satellite.
How many jobs can a Templater Bot queue?
A Templater error message states that Templater Bot can queue a max of 20 jobs at any given time.
How often does a Bot check for new data?
The default polling interval is 0.5 minutes, or 30 seconds. The minimum is 0.3 minutes for Google Sheets and 0.2 minutes for JSON sources.
What happens when QUE credits run out?
With QUE Meter, Templater Bot stops and is auto disabled when QUE Credits run out. It can be enabled after a refill.
Do I need a license for every render machine?
Templater registration is required for each machine that hosts a Templater installation. A Standard license is activated on one machine at a time, and a Floating key has seats that machines check out when one is released.