Skip to content

Understanding the Worker Slots Gauge #8741

@davidlbudiman

Description

@davidlbudiman

Hi, there!

I want to understand further on how to understand the Worker slots gauge. I tried to search the documentation but I couldn't make sense of it.

Here's more context:

  • Metrics Dashboard: DataDog
  • MaxConcurrentWorkflowTaskExecutionSize: 7500
  • MaxConcurrentLocalActivityExecutionSize: 7500
  • IsLocalActivityWorkerOnly: True
  • MaxConcurrentWorkflowTaskPollers: 2
  • Workflow avg latency: 50ms
  • Workflow max latency: 5min.
  • Expected incoming workflow per second: 1k and expected to increase on further development.
  • Duration of incoming workflow per second: Possibly 6 hours, there might be need to make the duration goes faster, which means incoming workflow per second will be higher based on the business requirements.

I wanted to increase the # of Workflows that can be taken per second. But, I don't understand the gauge. Because it kept showing at max it takes 7 for the WorkflowTask Workers. What does this 7 mean? Is it that the worker takes 7 workflows at that second, or is it that it creates 700% concurrent workflow tasks? How do I know the number of running workflows per seconds? The reason I'm focusing on MaxConcurrent*ExecutionSize, I find that increasing them seems to increase the concurrency of the workflows. But, am I right? How do I make sure of this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions