Add WorkerListInfo proto for efficient worker listing#724
Merged
Conversation
3 tasks
rkannan82
force-pushed
the
kannan/worker-summary-proto
branch
2 times, most recently
from
9e0ccf0 to
a12853c
Compare
bergundy
reviewed
Feb 27, 2026
## What changed? - Add `WorkerSummary` proto containing static/slow-changing worker fields - Update `WorkerInfo` to embed `WorkerSummary` and add dynamic fields separately - Deprecate `worker_heartbeat` field in `WorkerInfo` - Add `workers` field to `ListWorkersResponse` using `WorkerSummary` - Deprecate `workers_info` field in `ListWorkersResponse` ## Why? The current `ListWorkersResponse` returns full `WorkerInfo` which includes expensive dynamic metrics (CPU, memory, slot usage) that change frequently. For listing many workers, we only need static/slow-changing information. This change separates worker information into: - `WorkerSummary`: static fields for efficient listing - `WorkerInfo`: full details including dynamic metrics for DescribeWorker Made-with: Cursor
rkannan82
force-pushed
the
kannan/worker-summary-proto
branch
from
a12853c to
749ca5b
Compare
…ity conventions Follow the established naming pattern used by other CHASM entities: - ActivityExecutionListInfo (for ListActivityExecutions) - ScheduleListEntry (for ListSchedules) - BatchOperationInfo (for ListBatchOperations) This ensures WorkerListInfo follows the same "ListInfo/ListEntry" suffix convention for types returned in List API responses. Made-with: Cursor
rkannan82
changed the title
bergundy
approved these changes
Feb 27, 2026
yuandrew
reviewed
Feb 27, 2026
Contributor
yuandrew
left a comment
yuandrew
left a comment
There was a problem hiding this comment.
Changes LGTM, will we have a server side PR to pick these up? I'm good to approve once we're close to being ready to merge this in
rkannan82
force-pushed
the
kannan/worker-summary-proto
branch
from
6d33e77 to
3288bcf
Compare
Made-with: Cursor
rkannan82
force-pushed
the
kannan/worker-summary-proto
branch
from
3288bcf to
39cd2be
Compare
yuandrew
approved these changes
Mar 9, 2026
02strich
added a commit
that referenced
this pull request
Mar 18, 2026
* origin/master: Add poller autoscaling namespace capability (#723) Add request header annotation and resource-id fields (#728) Trampolining: addition of fields to remove the infinite loops for pinned wfs (#721) Add WorkerListInfo proto for efficient worker listing (#724) Add storage driver info to worker heartbeats (#722)
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
3 participants
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.
What changed?
WorkerListInfoproto for List API (follows CHASM entity conventions likeActivityExecutionListInfo,ScheduleListEntry)workersfield toListWorkersResponsereturningrepeated WorkerListInfoworkers_infofield inListWorkersResponseServer PR
Why?
Listing many workers with full
WorkerInfo(containing dynamic metrics) is expensive.WorkerListInfocontains only static/slow-changing fields for efficient listing.How did you test it?
Potential risks
None - backward compatible.