Sidekiq warnings

Product Support

AI-generated summary

In a discussion about Sidekiq memory usage on a virtual server with 8GB RAM, Ethsim2 questions whether 500MB is excessive and considers adding UNICORN_SIDEKIQ_MEMORY_KILLER_MAX_RSS: 1024 to app.yml. Jagster notes that 500MB may suffice for fresh installs but suggests 550MB+ for active sites. Ethsim2 reports success after setting the limit to 700MB, yet still sees warnings, noting the prior usage was only 0.1MB higher 4. Ed_S references other threads where UNICORN_SIDEKIQ_MAX_RSS is discussed as a solution, though unresolved cases exist. Ethsim2 mentions a rebuild warning about “memory overcommit must be enabled”. Ed_S confirms running with memory overcommit enabled, noting it’s not yet standard in official scripts, and also disables transparent huge pages for performance, though not critical for memory stability.

1

IMG_9808
IMG_98081206×408 81.9 KB

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
2

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 :joy:

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.

3

my last rebuild worked, with 700 set for this

4

IMG_0764
IMG_07641206×617 106 KB

it’s strange that i’m still getting warning, the previous one / before the app.yml change was 0.1MB higher

5

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

6

memory overcommit must be enabled

? from the rebuild process

7

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.)