# Errori 504 Gateway Time-out con 2 milioni di post migrati su forum vBulletin

**URL:** https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665
**Category:** Self-hosting
**Created:** [4 Gennaio 2019, 1:06am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665 "2019-01-04T01:06:22Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Brandon\_Martus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brandon_martus/32/127631_2.png) [@Brandon\_Martus](https://meta.discourse.org/u/Brandon_Martus)
#### Post date: [4 Gennaio 2019, 1:06am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665/1 "2019-01-04T01:06:22Z")

</div>

Ho una nuova installazione di Discourse, dove ho importato un forum vBulletin con circa 2 milioni di post e un numero di utenti attivi (concorrenti) giornalieri compreso tra 200 e 1000.

Lancio oggi su un droplet Digital Ocean con 6 vCPU e la navigazione del sito era piuttosto problematica all’inizio: molto lenta, errori 504, ecc. Ho ridimensionato l’istanza a 16 vCPU e ora funziona meglio, ma ricevo ancora spesso timeout 504.

Esiste una guida su cosa è possibile configurare in nginx per sfruttare meglio le risorse disponibili?

Il carico medio è ancora piuttosto elevato.

Qualche suggerimento?

Grazie!

**AGGIORNAMENTO** : Mi rendo conto di non aver ricostruito l’ambiente dopo il ridimensionamento; forse questo terrà conto delle nuove risorse?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [4 Gennaio 2019, 1:37am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665/2 "2019-01-04T01:37:04Z")

</div>

I believe @pfaffman may have some advice.

---

<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: [4 Gennaio 2019, 1:50am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665/3 "2019-01-04T01:50:14Z")

</div>

You should be on an “optimized” droplet. Cpu speed will be important for your level of traffic.

After you resize you should run

```
./discourse-setup

```

Again. It’ll adjust the memory settings. You can control-c after its first message and then

```
./launcher destroy app
./launcher start app

```

Rather than letting it rebuild. (a two container installation will reduce downtime during rebuilds)

Things are likely slow due to lots of sidekiq jobs.

If you’d like hands on help tuning your installation my contact information is in my profile.

---

<div class="post-metadata">

### Author: ![Brandon\_Martus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brandon_martus/32/127631_2.png) [@Brandon\_Martus](https://meta.discourse.org/u/Brandon_Martus)
#### Post date: [4 Gennaio 2019, 1:56am UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665/4 "2019-01-04T01:56:07Z")

</div>

Awesome, thanks for the quick reply.

I’ll give this a shot and contact you if I run into any more trouble.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [7 Dicembre 2021, 5:04pm UTC](https://meta.discourse.org/t/504-gateway-time-out-errors-with-2-million-post-migrated-vbulletin-forum/105665/5 "2021-12-07T17:04:55Z")

</div>