Skip to content

More language edits to resource-based slot suppliers#4286

Open
Sushisource wants to merge 4 commits intomainfrom
more-resource-based-changes
Open

More language edits to resource-based slot suppliers#4286
Sushisource wants to merge 4 commits intomainfrom
more-resource-based-changes

Conversation

@Sushisource
Copy link
Member

@Sushisource Sushisource commented Mar 13, 2026

What does this PR do?

Title

Notes to reviewers

┆Attachments: EDU-6042 More language edits to resource-based slot suppliers

@Sushisource Sushisource requested a review from a team as a code owner March 13, 2026 00:21
@vercel
Copy link

vercel bot commented Mar 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Mar 13, 2026 0:42am

Request Review

@github-actions
Copy link
Contributor

github-actions bot commented Mar 13, 2026

📖 Docs PR preview links

They provide excellent balance with built-in throttling that ensures the Worker will be cautious when handing out new executor slots.
- When very low Task completion latency & maximum throughput is important, avoid resourced-based auto-tuning slot suppliers.
- Reserve auto-tuned resource-based slot suppliers for deployments with workloads that have resource
usage patterns you don't fully understand, and don't care to. It can offer good-enough performance

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we make good-enough bold

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

- **You want acceptable performance with minimum effort**:
Resource-based suppliers can provide reasonable performance without the need for profiling your
workfload. They can be a great way to get started with new workloads. If a workload becomes very
performance-sensitive, it's worth your time to profile it and choose appropriate fixed-size numbers.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we should be more explicit:

performance-sensitive, we suggest profiling it and using fixed-size numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants