# Errore di carico estremo dopo l'aggiornamento a 3.3.0.beta3-dev ieri (on 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 Giugno 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:** 8

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [4 Giugno 2024, 9:08pm UTC](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399/8 "2024-06-04T21:08:18Z")

</div>

Questa è un’ipotesi, ma l’unica cosa che mi salta all’occhio nei log di Sidekiq è che il job mostrato è `NotifyMailingListSubscribers`. Quel job può potenzialmente creare molte richieste.

Inoltre, vedi errori nella tua pagina Admin / Log / Log Errori?

---

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