# Issue: Extremely Slow Sidekiq Processing After Large Imports on Multisite Instance

**URL:** https://meta.discourse.org/t/issue-extremely-slow-sidekiq-processing-after-large-imports-on-multisite-instance/363185
**Category:** Support
**Created:** [April 23, 2025, 5:10pm UTC](https://meta.discourse.org/t/issue-extremely-slow-sidekiq-processing-after-large-imports-on-multisite-instance/363185 "2025-04-23T17:10:59Z")
**Posts on this page:** 1
**Showing post:** 3

<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 23, 2025, 6:41pm UTC](https://meta.discourse.org/t/issue-extremely-slow-sidekiq-processing-after-large-imports-on-multisite-instance/363185/3 "2025-04-23T18:41:24Z")

</div>

The answer to all of those questions is, more or less, cranking up `DISCOURSE_SIDEKIQ_WORKERS`.

I would crank that up to maybe 32 since you know you have a lot of spare CPU available. If you still have lots of CPU available after that’s been running for a while, feel free to crank it up more.

You could probably drop that back down to, say, 8 or 12 for normal operation.

Make sure you have enough `max_connections` for postgres. You’ve probably already bumped it up since you’re running multisite, but keep an eye on it.

---

_[View the full topic](https://meta.discourse.org/t/issue-extremely-slow-sidekiq-processing-after-large-imports-on-multisite-instance/363185)._