# Performance Limitations of Workers

**URL:** https://community.temporal.io/t/performance-limitations-of-workers/8563
**Category:** Community Support
**Created:** [June 19, 2023, 6:07am UTC](https://community.temporal.io/t/performance-limitations-of-workers/8563 "2023-06-19T06:07:43Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![lyq](https://avatars.discourse-cdn.com/v4/letter/l/91b2a8/32.png) [@lyq](https://community.temporal.io/u/lyq)
#### Post date: [June 19, 2023, 6:07am UTC](https://community.temporal.io/t/performance-limitations-of-workers/8563/1 "2023-06-19T06:07:43Z")

</div>

In the production environment, I have millions of pipelines to execute, and each pipeline corresponds to a PipelineWorkflow class with @WorkflowInterface annotations, and some of the subjobs of the pipeline correspond to a PipelineActivities class with @ActivityInterface annotations. Will there be performance pressure when millions of pipelines and sub-jobs are registered with one worker, that is, all of them share a taskqueue?

---

<div class="post-metadata">

### Author: ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [June 19, 2023, 5:51pm UTC](https://community.temporal.io/t/performance-limitations-of-workers/8563/2 "2023-06-19T17:51:04Z")

</div>

The performance limitation is mainly related to the number of actions per second across all these pipelines. Each worker would have limited throughput. So more workers might be needed to execute at higher rates.

---

<div class="post-metadata">

### Author: ![lyq](https://avatars.discourse-cdn.com/v4/letter/l/91b2a8/32.png) [@lyq](https://community.temporal.io/u/lyq)
#### Post date: [June 20, 2023, 3:41am UTC](https://community.temporal.io/t/performance-limitations-of-workers/8563/3 "2023-06-20T03:41:11Z")

</div>

However, for millions of pipelines, when many workers are created, an error indicating that resources exceed the limit is reported.

---

<div class="post-metadata">

### Author: ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [June 20, 2023, 2:27pm UTC](https://community.temporal.io/t/performance-limitations-of-workers/8563/4 "2023-06-20T14:27:08Z")

</div>

Open workflows that are waiting on something don’t consume worker resources. We need more information about which exact resource limit is reported to help you.