Repository navigation
Resource-aware executor scheduling - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes router and executor placement resource-aware so VM starts are limited by aggregate CPU, memory, and VM slots instead of VM count alone. This lets mixed-size jobs share a host when they fit while keeping oversized concurrent jobs queued.
Changes
Testing
swift test --package-path Packages/TartCommonswift test --package-path Packages/RouterAppswift test --package-path Packages/ExecutorAppswiftlint lint --quiet --config .swiftlint.ymlswift buildwas blocked while downloading the external SwiftLint artifact; the changed packages compiled and passed independently.Ticket: NO-TICKET (no Jira ticket)