Updates Poller Autoscaler Content #3958
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
📖 Docs PR preview links
|
Sushisource
reviewed
Oct 23, 2025
docs/develop/worker-performance.mdx
Outdated
|
|
||
| Task Pollers enable efficient load balancing across multiple Worker processes. | ||
| The number of Task Pollers can be configured using `WorkerOptions` when creating a new Worker instance. | ||
| Temporal SDKs implement support for *Automated Poller Tuning*, which dynamically adjusts the number of pollers in use to maximize throughput for a given number of workers and the size of the task backlog. |
There was a problem hiding this comment.
Let's call this Poller Autoscaling to match the behavior names in the code
docs/develop/worker-performance.mdx
Outdated
| Task Pollers enable efficient load balancing across multiple Worker processes. | ||
| The number of Task Pollers can be configured using `WorkerOptions` when creating a new Worker instance. | ||
| Temporal SDKs implement support for *Automated Poller Tuning*, which dynamically adjusts the number of pollers in use to maximize throughput for a given number of workers and the size of the task backlog. | ||
| Temporal recommends using Automated Poller Tuning for the majority of use cases, as manually setting this value too high or too low for your workload will result in decreased performance. |
There was a problem hiding this comment.
Suggested change
| Temporal recommends using Automated Poller Tuning for the majority of use cases, as manually setting this value too high or too low for your workload will result in decreased performance. | |
| Temporal recommends using Automated Poller Tuning for the majority of use cases, as manually setting the number of pollers too high or too low for your workload will result in decreased performance. |
docs/develop/worker-performance.mdx
Outdated
| GO SDK: https://pkg.go.dev/go.temporal.io/sdk/worker#PollerBehaviorAutoscalingOptions | ||
| ```go | ||
| w := worker.New(c, "my-task-queue", worker.Options{ | ||
|
|
There was a problem hiding this comment.
Can get rid of the extra empty lines between assignments in all these
docs/develop/worker-performance.mdx
Outdated
| Pollers create long-polling connections to the Temporal Service, allowing the service to dispatch Tasks to Workers. | ||
| When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. | ||
| A Worker's **Task Pollers** play a crucial role in the Temporal architecture by efficiently ingesting work to Workers to support scalable, resilient Workflow Execution. | ||
| Pollers create long-polling connections to the Temporal Service and actively poll a Task Queue for Tasks to process. When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. |
There was a problem hiding this comment.
Suggested change
| Pollers create long-polling connections to the Temporal Service and actively poll a Task Queue for Tasks to process. When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. | |
| Pollers create long-polling connections to the Temporal Service and actively poll a Task Queue for Tasks to process. When a Task Poller receives a Task, it delivers the Task to the appropriate Executor Slot for processing. |
bchav
changed the title
Adds sdktabs import statements that will (hopefully) fix the broken build
Attempt to fix markdown-fu
docs/develop/worker-performance.mdx
Outdated
| Pollers create long-polling connections to the Temporal Service, allowing the service to dispatch Tasks to Workers. | ||
| When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. | ||
| A Worker's **Task Pollers** play a crucial role in the Temporal architecture by efficiently ingesting work to Workers to support scalable, resilient Workflow Execution. | ||
| Pollers create long-polling connections to the Temporal Service and actively poll a Task Queue for Tasks to process. When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. |
There was a problem hiding this comment.
Suggested change
| Pollers create long-polling connections to the Temporal Service and actively poll a Task Queue for Tasks to process. When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. | |
| Pollers create long-polling connections to the Temporal Service and actively poll a Task Queue for Tasks to process. When a Task Poller receives a Task, it delivers to the appropriate Executor Slot for processing. |
flippedcoder
approved these changes
Oct 24, 2025
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.
Adds detail about Poller Autoscaler feature, recommends use, provides SDK snippets
Please check my formatting on the SDKtab example, not sure how this will build out :)