I use discourse_docker to generate Docker image, then deploy to kubernetes. In my container/web_only.yml: env: UNICORN_WORKERS: 2 However, if I execute top in the container, I can see 4 workers: [image] Is it out of control, or did I missed something?

That controle the number of unicorn workers but that isn’t the only thing in the container. We also run sidekiq, nginx, etc. Sidekiq also shows as Ruby in top until you press c

Thank you. I see. So is this the minimum configuration for a low-traffic site? I set a maximum memory usage of 1GB to the container and it got OOM a few times. [image]

Our recommended configuration is at least 2G of RAM + 2G of swap.

Yeah, I understand. The “recommended” configuration, I guess, is for a real “community”. My instance, however, is only a support forum for my personal project with really low traffic (really). I know bigger RAM can always solve the problem, but it would be great if I can get some ideas on RAM optimization so I don’t have to upgrade my server with actually no need:)

The minimum is 1GB Ram with 2GB Swap. And if you follow the official install guide we automatically set swap for you. Did you get OOM with swap?

[imagem] Vencent: some ideas on RAM optimization You could probably get away with one unicorn (you have two now) and one sidekiq.

[imagem] RGJ: You could probably get away with one unicorn (you have two now) and one sidekiq. That is what I’m thinking. Does that mean my whole site will block if a single request is doing I/O (i.e. database read)? I’m not really familiar with the tech details in Discourse but it seems likely to happen.

[imagem] Falco: Did you get OOM with swap? No, I disabled swap because my cloud service provider suggests me to. I also heard it’s better to disable swap on a Kubernetes node. Maybe I should try to loose the RAM limit for Discourse and see what happens.

[imagem] Vencent: No, I disabled swap because my cloud service provider suggests me to. Well, so that is an unsupported configuration. Good luck with the experiments, but that is not a setup we support.

[imagem] Vencent: I also heard it’s better to disable swap on a Kubernetes node. Yes, but that’s in the same league as “it’s better to have more RAM” . And if you don’t have more RAM then you should have swap as a fallback. [imagem] Vencent: my whole site will block if a single request is doing I/O (i.e. database read)? No, it won’t be THAT bad. But you said you had really low traffic…

O processo do worker está mais do que definido?

Suporte ao Produto Instalação

RGJ (Richard - Communiteq) 2 Abril , 2019 15:58 7

You could probably get away with one unicorn (you have two now) and one sidekiq.

Tópico		Respostas	Vistas
Limiting the number of unicorns, memory usage and swapping Self-hosting server-resources	4	1060	11 Novembro , 2023
How much RAM is needed to host discourse along with other services? Self-hosting unsupported-install , hosting	8	2517	18 Maio , 2024
Discourse-docker run with unicorn memory issue Self-hosting server-resources	6	1210	23 Dezembro , 2019
Recommendation for number of workers: cores × 2? Self-hosting	16	756	29 Abril , 2025
Browser upgrade fails when discourse is configured to use one unicorn worker Bug	5	545	18 Outubro , 2023

O processo do worker está mais do que definido?

Related topics