# שגיאת עומס קיצונית לאחר שדרוג ל-3.3.0.beta3-dev אתמול (ב-prem)

**URL:** https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399
**Category:** Self-hosting
**Created:** [3 ביוני,‏ 2024,‏ 7:17pm UTC](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399 "2024-06-03T19:17:43Z")
**Posts on this page:** 1
**Showing post:** 13

<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: [5 ביוני,‏ 2024,‏ 3:31pm UTC](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399/13 "2024-06-05T15:31:21Z")

</div>

> [@Jose\_C\_Gomez](#):
>
> Would spinning more unicorns help?

Yes, that would probably help.

```plaintext
env:
  UNICORN_WORKERS: 8

```

in the app.yml will do this.

I recommend pulling performance numbers using the [prometheus plugin](https://meta.discourse.org/t/discourse-prometheus/72666) if you have that set up, or you can use [performance headers](https://meta.discourse.org/t/troubleshooting-severe-performance-issues-with-latest-discourse/182995/12).

Analysing your web logs should help a lot with identifying why your server is so busy; looks like crawlers are a good place to start.

---

_[View the full topic](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399)._