in a virtual server with 8GB RAM, i don’t suppose sidekiq using slightly more than 500M is an issue?
i’m interested whether to add the following line in my app.yml
env:
UNICORN_SIDEKIQ_MEMORY_KILLER_MAX_RSS: 1024
1 Like
Tot RAM doesn’t help here. It is kind of same thing than with amount of workers in the PHP-world and how much memory is allocated. Well, totally different thing, but yet 
My experiances are saying that 500 is enough for totally fresh installs, when there isn’t practically any components and plugins in use, nor users. 550+ at least is needed.
1 Like
my last rebuild worked, with 700 set for this
1 Like
it’s strange that i’m still getting warning, the previous one / before the app.yml change was 0.1MB higher
In this other thread I see a different setting is mentioned
Sidekiq is consuming too much memory
But I also see an unresolved similar situation relatively recently in
Sidekiq is consuming too much memory even with UNICORN_SIDEKIQ_MAX_RSS adjusted
2 Likes
memory overcommit must be enabled
? from the rebuild process
Yes, I’ve always run with memory overcommit, and posted about it several times. Others also run this way, but I have the feeling that it’s not understood and accepted enough to have made it into official scripts or recipes.
(I’ve also disabled transparent huge pages, but that’s a mere performance issue, rather than a make-or-break for small-memory systems.)
1 Like