Skip to content

docs: update worker tuner type guidance#4601

Open
lennessyy wants to merge 7 commits into
mainfrom
worker-slot-supplier-issue
Open

docs: update worker tuner type guidance#4601
lennessyy wants to merge 7 commits into
mainfrom
worker-slot-supplier-issue

Conversation

@lennessyy
Copy link
Copy Markdown
Contributor

@lennessyy lennessyy commented May 21, 2026

What does this PR do?

Notes to reviewers

┆Attachments: EDU-6402 docs: update worker tuner type guidance

@vercel
Copy link
Copy Markdown

vercel Bot commented May 21, 2026

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

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment May 21, 2026 8:15pm

Request Review

@lennessyy lennessyy changed the title docs: update worker supplier type guidance docs: update worker tuner type guidance May 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 21, 2026

📖 Docs PR preview links

@lennessyy lennessyy marked this pull request as ready for review May 21, 2026 00:37
@lennessyy lennessyy requested a review from a team as a code owner May 21, 2026 00:37
Comment thread docs/develop/worker-performance.mdx Outdated
fixed-size tuner with appropriately chosen configuration, but can offer reasonable performance
without the need for profiling.
Resource-based slot suppliers are suited to specific use cases.
A properly configured fixed-size tuner often delivers better performance, so reserve resource-based suppliers for the following scenarios:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maybe a bit redundant, we've already stated this earlier:

A fixed-size tuner with appropriately chosen values delivers better performance and more predictable behavior than a resource-based tuner.

Comment thread docs/develop/worker-performance.mdx Outdated
A fixed-size tuner with appropriately chosen values delivers better performance and more predictable behavior than a resource-based tuner.

When choosing whether to opt for fixed assignment or resource-based suppliers, consider:
Each SDK provides sensible defaults for fixed-size slot counts.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I might suggest removing the word sensible. The comment is a bit tongue-in-cheek, but the default values are often not ideal

Comment thread docs/develop/worker-performance.mdx Outdated
Each SDK provides sensible defaults for fixed-size slot counts.
See [Compute defaults by SDK](/develop/worker-tuning-reference#compute-defaults-by-sdk) for the default values per language.
Start with these defaults and adjust based on profiling.
Workflow Tasks make minimal demands on CPU and memory, so their slot counts rarely need tuning.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would not suggest this. Number of workflow task slots should be dependent on the workload.

Comment thread docs/develop/worker-performance.mdx Outdated
Comment thread docs/develop/worker-performance.mdx Outdated
Co-authored-by: Lenny Chen <55669665+lennessyy@users.noreply.github.com>
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.

3 participants