Schedules with Heavy Processing¶
For resource-intensive order runs—for example, those with large queries, heavy use of variables, or data sources and sinks—you can adjust memory and disk space allocations in the schedule form. Default maximums are 1024 MB of RAM and 2048 MB of disk space.
If an order run passes the maximum resources set, the order run is automatically stopped.
Additionally, parallel nodes run concurrently by default. A high number of parallel nodes can overload the data sources or processing systems they interact with. The maximum number of nodes to run in parallel at any given time during an order run can be limited by the maximum threads resource setting. Each thread runs one node at a time.
Resources for all order runs¶
Variation-level resource settings affect an overall order run and the temporary storage used by data sources and data sinks; they are not relevant to processing that occurs inside a container node.
How to¶
Start by configuring a schedule. In the Max RAM, Max Disk Space and Max Threads fields, specify resource values. Run a variation with that schedule to activate these settings.
Tip
Resources for container nodes: container settings only affect a container node itself. Here, boosting RAM and disk can help with heavy processing needs by running scripts within that container. Assign resource values from the Configuration tab of the Node Editor.
Run-once orders¶
When you apply a schedule to a variation and activate that scheduled order, the system will allocate resources—up to the specified max RAM and max disk space settings—to every order run performed for that schedule. You can use an empty schedule to allocate resources for orders that run once.
How to¶
To set resource maximums for run-once orders, create a schedule without a frequency and only enter values for the schedule name, max RAM, max disk space and maximum number of threads.
For more information, see Run-Once Order Schedules.