chore: Convert sample job templates to use task chunking for Nuke, Maya, VRED and 3dsMax/Vray#183
Conversation
github-actions
bot
added
the
waiting-on-maintainers
|
|
||
| - **Scene File**: 3ds Max scene file (.max) to render | ||
| - **Frames**: Frame range specification (supports both `1-100` and `1,5,10-20` formats) | ||
| - **Frames**: Frame range to render (e.g., `0-10`) |
There was a problem hiding this comment.
Customer can still submit noncontiguous frames like 1,5,10-20 for contiguous rendering. Scheduler will break it up into contiguous chunks.
We should keep the old statement here
There was a problem hiding this comment.
Thanks for catching this. Updated it. 🙏
|
|
||
| ## Task Chunking | ||
|
|
||
| This job bundle uses the [Task Chunking](https://github.com/OpenJobDescription/openjd-specifications/blob/mainline/rfcs/0001-task-chunking.md) extension with `rangeConstraint: CONTIGUOUS` for efficient parallel rendering. |
There was a problem hiding this comment.
efficient parallel rendering
One feedback I got from my other chunking sample PR was TaskChunking does not make it more efficient in parallel rendering, we already do that. We should both remove this from our READMEs :)
There was a problem hiding this comment.
FYI. This is the feedback I received:
This needs a small adjustment. The reason for chunking is to reduce overhead by running chunks of short-running tasks together instead of scheduling each one individually. Chunking reduces parallelism. Particularly our new adaptive chunking mode is about automatically load balancing work more efficiently.
There was a problem hiding this comment.
Thank you! I updated the README files to have something like, reduce scheduling overhead by grouping frames into chunks..
| This job bundle demonstrates rendering 3ds Max scenes with V-Ray, including automatic VRIMG to EXR conversion with denoising preservation and intelligent frame chunking. | ||
| This job bundle demonstrates rendering 3ds Max scenes with V-Ray, including automatic VRIMG to EXR conversion with denoising preservation, using the Open Job Description task chunking extension for efficient multi-frame rendering. | ||
|
|
||
| ## Task Chunking |
There was a problem hiding this comment.
We don't support chunking from the submitter, so I will be more careful here.
Can we only change examples that have submitters that support chunking?
There was a problem hiding this comment.
Thanks for the feedback. My understanding is that these examples are intended to submit via Deadline CLIs. https://github.com/aws-deadline/deadline-cloud-samples?tab=readme-ov-file#job-bundle-samples Since these sample bundles don't go through the DCC submitters, they shouldn't be affected by whether the submitter plugins support chunking yet. Let me know if you have any concerns though — happy to discuss further!
…ya, Vred, and 3dsmax/Vray Signed-off-by: Haejung Choi <chaejung@amazon.com>
diane-hj
force-pushed
the
add-task-chunking-example
branch
from
17dc051 to
f2aaa6f
Compare
Cherie-Chen
removed
the
waiting-on-maintainers
3 participants
Convert sample job templates to use task chunking for Nuke, Maya, VRED and 3dsMax/Vray
What was the problem/requirement? (What/Why)
Now we support Task Chunking, we should update our sample job templates to use it.
What was the solution? (How)
Convert sample job templates to use task chunking. In this PR, it converts sample job templates for Nuke, Maya, VRED, and 3dsMax/Vray
What is the impact of this change?
User will have sample job templates using task chunking for the DCC they are working with.
How was this change tested?
I submitted job using these job templates and here is the results:
Was this change documented?
Yes, this PR also included doc changes
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.