[Trigger] RAM
Q100024: [Trigger] RAM
Checks available RAM and fires when specified condition is met
| Parameter | In/Out | Description | Other Info |
|---|---|---|---|
| Threshold | In | Threshold amount to compare available RAM against. | Default: 90 |
| Threshold Units | In | Choices: %, Kilobytes, Megabytes, Gigabytes, Terabytes, PetabytesThe type of value the threshold is comparing against. |
Default: Percentage |
| Trigger threshold | In | Choices: Above, BelowShould this be triggered when the amount of available RAM crosses the line defined and remains above/below the specified threshold value? |
Default: Below |
| Output scale | InOut | Choices: Kilobytes, Megabytes, Gigabytes, Terabytes, PetabytesThe scaling of the output values. Typically set to same as the Threshold Type except when that is using percentage. |
Default: MB |
| Seconds between checks | In | How often to check, in seconds (multiples of 5) | |
| Seconds before triggering | In | The conditions must be satisfied for at least this many seconds before the trigger is executed (0 = instantly) | |
| Seconds between triggers | In | After triggering, allow at least this many seconds to pass before triggering again (0 = no time limit) | |
| MemoryAvailable | Out | The amount of available memory. The value is scaled in accordance to the OutputScale setting. |
|
| MemorySize | Out | The total memory size. The value is scaled in accordance to the output scale setting. |
(Italics = required parameters)
Notes
This trigger allows a job to be started if the percentage of available RAM raises above, or drops below, a certain point. The parameters allow for tuning the trigger for the specific machine it is installed on. Exercise caution using this trigger, as it has the potential to cause high resource utilization if you have not tuned the settings well for your given server and start executing a job with heavy resource usage.
Last Updated:
1/28/2026 4:28:03 PM