Using a Scaled Out Executor
A scaled Executor component instance has multiple execution nodes, or gears, on which executions may be scheduled. Once it has been scaled out, you can use a scaled Executor component instance in exactly the same way as an un-scaled one—submitting executions using REST or SOAP webservices, waiting until they complete, then downloading the results.
When the component is scaled, the Concurrency Level configuration setting controls how many concurrent executions are permitted on each gear. For example, an Executor component scaled across four gears with the concurrency level set to 3 may have up to twelve executions in progress at the same time. Incoming executions may be started on any gear that is not at capacity, note that no attempt is made to balance the load equally between gears. In this example, if we queue six executions, they may all be started on two of the gears, while the other two gears remain idle until more executions are queued.
Only the Staging and Production lifecycle stages of the component may be scaled out. The Design instance must never be scaled out.