# Optimizing a Large Discourse Multisite: Database and Sidekiq Bottlenecks

**URL:** https://meta.discourse.org/t/optimizing-a-large-discourse-multisite-database-and-sidekiq-bottlenecks/381363
**Category:** Self-hosting
**Tags:** multisite, hosting
**Created:** [September 2, 2025, 8:16pm UTC](https://meta.discourse.org/t/optimizing-a-large-discourse-multisite-database-and-sidekiq-bottlenecks/381363 "2025-09-02T20:16:41Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 3, 2025, 12:36am UTC](https://meta.discourse.org/t/optimizing-a-large-discourse-multisite-database-and-sidekiq-bottlenecks/381363/3 "2025-09-03T00:36:25Z")

</div>

> [@emonunix](#):
>
> How should `DISCOURSE_SIDEKIQ_WORKERS` be sized in a multisite environment to handle a high job volume without stressing the database?

Sounds like you need fewer?

I’m pretty sure that it already knows to prioritize the high priority jobs.

---

_[View the full topic](https://meta.discourse.org/t/optimizing-a-large-discourse-multisite-database-and-sidekiq-bottlenecks/381363)._