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.
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:)
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.
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.
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.
No, it won’t be THAT bad.
But you said you had really low traffic…