Please help me understand PDGDeadline

   3059   22   4
User Avatar
Member
8764 posts
Joined: 7月 2007
Offline
Are the partitions you are talking about something on Deadline side?
Since if you mean wrapping all work items into a single partition on TOP side then I imagine you lose granular dependencies on input workitems essentially becoming wait for all, which can be undesirable in many scenarios and also is not very friendly towards true dynamic workitems or mixed with other type of partitioning since this sounds like otherwise unnecessary additional partition wrapper and I dont know if you can nest partitions
Tomas Slancik
FX Supervisor
Method Studios, NY
User Avatar
Member
40 posts
Joined: 5月 2019
Offline
Indeed we mean waiting for all/part of upstream tasks. Partitions could contain batches that are directly translated to batches in Deadline. The way Deadline works, it takes a frame range and a path template, and manages itself to determine job tasks.
It's true that we might lose some efficiencies this way, but it will be solid, an avoid the race condition of dynamically producing DL tasks.
Edited by monomon - 2024年10月8日 03:57:20
User Avatar
Member
82 posts
Joined: 11月 2017
Offline
Partitions are on the houdini side - when we have work items that are per frame, we can partition them into work items that are per job. Deadline needs the frame range for the job, we can provide that from a work item attribute.
  • Quick Links