feat: Implement resource requirements for components#194
Open
feat: Implement resource requirements for components#194
Conversation
Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add resource requirements for components
feat: Implement resource requirements for components
Jan 28, 2026
toby-coleman
requested changes
Jan 31, 2026
Contributor
toby-coleman
left a comment
There was a problem hiding this comment.
@copilot see comments
…r, move imports to top Co-authored-by: toby-coleman <13170610+toby-coleman@users.noreply.github.com>
…ource-requirements
|
Benchmark comparison for |
|
Benchmark comparison for |
|
Benchmark comparison for |
toby-coleman
approved these changes
Feb 7, 2026
|
Benchmark comparison for |
|
Benchmark comparison for |
|
Benchmark comparison for |
|
Benchmark comparison for |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
Adds resource specification support for components to enable Ray actor resource allocation and Tuner placement group optimization.
Changes
Core Schema
ResourcePydantic class inplugboard_schemas.componentwith fields:cpu,gpu,memory(integer bytes),resources(custom dict)n,u,m,k,M,G,T,P,E(e.g.,"250m"→ 0.25,"5k"→ 5000)Ki,Mi,Gi,Ti,Pi,Ei(e.g.,"10Mi"→ 10,485,760 bytes)cpu=0.001, others zeroto_ray_options()for Ray actor configurationComponent Integration
Component.__init__()with optionalresourcesparameterComponentArgsDict,ComponentArgsSpecfor YAML supportRay Execution
RayProcess._create_component_actor()to apply resource requirements viaray.remote(**ray_options)Resource()when unspecifiedTuner Optimization
Tuner._calculate_placement_bundles()to aggregate component resourcesPlacementGroupFactorywith tuner overhead (0.5 CPU) + component bundleDocumentation
docs/examples/tutorials/running-in-parallel.mdreferencing resource requirements exampleUsage Example
Tests
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.