# Recommendation for number of workers: cores × 2?

**URL:** https://meta.discourse.org/t/recommendation-for-number-of-workers-cores-x-2/363055
**Category:** Self-hosting
**Created:** [April 22, 2025, 2:48pm UTC](https://meta.discourse.org/t/recommendation-for-number-of-workers-cores-x-2/363055 "2025-04-22T14:48:20Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [April 25, 2025, 6:58pm UTC](https://meta.discourse.org/t/recommendation-for-number-of-workers-cores-x-2/363055/16 "2025-04-25T18:58:43Z")

</div>

> [@Editor0732](#):
>
> How many workers should I increase?

BTW here is what Falco was looking at to make that recommendation:

 ![The image is a line graph showing active web requests over time with spikes at 22:45 and 00:00, and queued requests being highlighted with a red arrow. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/d/5/a/d5a3be3195bd79faa16dbb027f9272b4007a06ed.png)

I’d bump 8 → 12. Gives you some headroom and should clear out those queues.

That large spike, BTW, is indicative of the other requests waiting on… something, probably a common lock. Perhaps a megatopic post.

If you can get postgres usage metrics as well, that would be useful.

> [@Editor0732](#):
>
> There are many mega topics in our Discourse

megatopics are a weak spot, see [Improving Instance Performance (Megatopics, Database Size and Extreme Load)](https://meta.discourse.org/t/improving-instance-performance-megatopics-database-size-and-extreme-load/144277)

Consider breaking these up or using chat instead (I see your largest one with 8.9k replies is explicitly a chat room).

---

_[View the full topic](https://meta.discourse.org/t/recommendation-for-number-of-workers-cores-x-2/363055)._