AWS Security ChangesHomeSearch

AWS deadline-cloud documentation change

Service: deadline-cloud · 2025-05-10 · Documentation low

File: deadline-cloud/latest/developerguide/build-jobs-scheduling.md

Summary

Added new section explaining session actions pipelining mechanics and scheduling logic

Security assessment

Documentation update focuses on performance optimization and task scheduling mechanics rather than security controls. No security-related terminology or vulnerabilities addressed.

Diff

diff --git a/deadline-cloud/latest/developerguide/build-jobs-scheduling.md b/deadline-cloud/latest/developerguide/build-jobs-scheduling.md
index 87154d528..f2d3fc646 100644
--- a//deadline-cloud/latest/developerguide/build-jobs-scheduling.md
+++ b//deadline-cloud/latest/developerguide/build-jobs-scheduling.md
@@ -164,0 +165,25 @@ The following job template has a step environment. It has an `onEnter` definitio
+### Session actions pipelining
+
+Session actions pipelining lets a scheduler pre-assign multiple session actions to a worker. The worker can then run these actions sequentially, reducing or eliminating idle time between tasks.
+
+To create an initial assignment, the scheduler creates a session with one task, the worker completes the task, and then the scheduler analyzes the task duration to determine future assignments.
+
+For the scheduler to be effective, there are task duration rules. For tasks under one minute, the scheduler uses a power-of-2 growth pattern. For example, for a 1-second task, the scheduler assigns 2 new tasks, then 4, then 8. For tasks over one minute, the scheduler assigns only one new task and pipelining remains disabled.
+
+To calculate pipeline size, the scheduler does the following:
+
+  * Uses average task duration from completed tasks
+
+  * Aims to keep the worker busy for one minute
+
+  * Considers only tasks within the same session
+
+  * Does not share duration data across workers
+
+
+
+
+With session actions piplelining, workers start new tasks immediately and there's no waiting time between scheduler requests. It also provides improved worker efficiency and better task distribution for long-running processes.
+
+Additionally, if there is a new higher priority job available, the worker will finish all of its previously assigned work before its current session ends and a new session from a higher priority job is assigned.
+