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
סיכום מבוסס בינה מלאכותית
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.
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.
הבנייה מחדש האחרונה שלי הצליחה, עם 700 שנקבעו לכך
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
memory overcommit must be enabled
? מתהליך הבנייה מחדש
כן, תמיד הרצתי עם memory overcommit, ופרסמתי על כך מספר פעמים. אחרים גם רצים כך, אבל יש לי תחושה שזה לא מובן ומקובל מספיק כדי להיכנס לסקריפטים או מתכונים רשמיים.
(גם השבתתי דפי ענק שקופים, אבל זו בעיית ביצועים בלבד, ולא בעיה קריטית למערכות עם זיכרון קטן.)