My Discourse is doing great, but I’ve been checking my logs and sometimes the connection times out. I know this is not a Discourse problem per se, and more of a Docker one, but it might be useful for newbies (like me) to know how to tune our Nginx, Docker or Discourse to avoid this. I already remov…

That’s an indication that you don’t have enough Unicorn workers for the number of requests your site is seeing. Consider increasing the UNICORN_WORKERS setting in your app.yml and rebuilding (you might need to get more RAM to accommodate the larger number of workers).

Thanks! I have 8GB of RAM, what amount of workers do you suggest? I do have other sites running it on, a few. It’s set now to the default that’s commented out: env: LANG: en_US.UTF-8 ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2…

General advice is one worker per CPU core (real or logical). I would allow at least 512mb ram per worker as well, so here is hoping you have at least 512mb times the number of logical cores on your server :wink:

Thanks! Just did it. Hope it works :smiley:

Ok I just set it to 6 workers (as I have a Linode 8096: 8 GB RAM, 6 CPU Cores, 192 GB SSD Storage https://www.linode.com/pricing ) env: LANG: en_US.UTF-8 ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 UNICORN_WORKERS: 6 ## #…

[imagem] codinghorror: Not sure message bus polling timeouts really matter though. Message bus is used to poll for updates (e.g. new posts, threads) and update the page?

Yes but a “failure” there would never be visible to the user, and may not matter. Since the bus is always active, more messages will arrive later…

Based on your feedback I added a line to clarify that Unicorns should scale with CPU cores, when possible ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 ## If you have lots of memory, use one or two workers per logical CPU core #UNICOR…

(This is an old topic, but it still seems like where this belongs) [imagem] codinghorror: one worker per CPU core (real or logical). I would allow at least 512mb ram per worker So the “ram per worker” is db_work_mem? That seems right, but the comments there don’t seem to say what you said ab…

How to avoid upstream timeouts?

Product Support

codinghorror (Jeff Atwood) 12 Novembro , 2015 07:09 7

Make sure you have upped database ram in app.yml. Other than that and adjusting number of unicorn workers, that’s about all I can think of. Not sure message bus polling timeouts really matter though.

Tópico		Respostas	Vistas
Due to extreme load, this is temporarily being shown to everyone... when it's not really the case Self-hosting server-resources	19	2023	21 Julho , 2023
Recommendation for number of workers: cores × 2? Self-hosting	16	729	29 Abril , 2025
High CPU usage (Ruby) Product Support server-resources	20	1096	3 Fevereiro , 2025
Best configurations for speeding up standalone discourse Self-hosting server-resources	25	4698	14 Fevereiro , 2024
502 Bad Gateway for only two Topics Self-hosting arm	19	2287	17 Novembro , 2022

How to avoid upstream timeouts?

Related topics