-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cuebot reserve all cores #1313
Cuebot reserve all cores #1313
Conversation
…t. Let it pass when they match.
…nt. Let it pass when it matches.
…o be used during dispatch
…o be used during dispatch (LocalHost)
…as not threadable.
doc: added some comments doc: Added some documentation doc: fix docstrings and parameters doc: added debug message doc: explain why we allow negative value doc: update debug message for rqd
669be2d
to
cc0f3a9
Compare
…o cuebot-reserve-all-cores
Very interesting addition, thanks for sending this! I haven't dug into this much yet but I brought it up during the TSC meeting, we're going to discuss some more. One thing to note -- we'll definitely want to wrap this in a flag so it can be turned on and off. Scheduling changes are always tricky and we don't want to disrupt other folks too much. |
@DiegoTavares Let me know if y'all have thoughts on this. |
@bcipriano Would you recommand it to be on or off by default ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO we should default to keeping this feature disabled. Very well implemented and an interesting feature to have.
Would you mind writing a blog post explaining the concept and how to use it?
Thanks for the review. I don't have access to a Linux farm at the moment, but we are doing a Windows set-up very soon. |
Thanks Kern
…_____________________________________
Diego Tavares da Silva
***@***.***
***@***.***
On Tue, May 21, 2024 at 10:32 AM Kern Attila GERMAIN < ***@***.***> wrote:
IMO we should default to keeping this feature disabled. Very well
implemented and an interesting feature to have.
Would you mind writing a blog post explaining the concept and how to use
it?
Thanks for the review.
I don't have access to a Linux farm at the moment, but we are doing a
Windows set-up very soon.
I'll need a bit more time for this one, and I will try to have that blog
post ;)
—
Reply to this email directly, view it on GitHub
<#1313 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXQ22BGDF3GFM45ZK7CT3ZDOAJ3AVCNFSM6AAAAAA37FUL5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTGEYTCMBVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…o cuebot-reserve-all-cores # Conflicts: # cuebot/src/main/java/com/imageworks/spcue/dispatcher/HostReportHandler.java
Signed-off-by: Kern Attila GERMAIN <[email protected]>
…ting "ALL" or "ALL (-x)".
… the new negative cores feature.
@bcipriano Would that work for you ? |
da2fe01
into
AcademySoftwareFoundation:master
Link the Issue(s) this Pull Request is related to.
Fixes #1297
Summarize your change.
As in many render engines, we should be able to set a negative core requirement.
minCores=8 > reserve 8 cores
minCores=0 > reserve all cores
minCores=-2 > reserve all cores minus 2
This PR addresses this feature by handling negative core requests.
Cuebot will try to match this number against the number of cores on each host.
The frame will be booked only if all cores are available in this scenario.
If the host is busy (even slightly), the frame is not booked, to avoid filling the remaining cores.
Testing
I would need some guidance to create proper tests for cuebot.
Screenshot
Update:
There is now a "ALL" text for zero cores, or "ALL (-2)" for negative cores reservation.
(cuesubmit feature in another PR #1284)