Added by Deryk Lister over 5 years ago
I just upgraded to OpenProject 10 (from 9) on CentOS 7 and the RAM usage has absolutely skyrocketed - in fact it filled the RAM, filled swap and choked the server. This is on a clean installation as we just started using it.
Where before there were 2 ruby processes, now there are 30.
Is there any way to make it use fewer ruby processes and bring the resource consumption back down a tad?
Found a threads_max_count in /opt/openproject/config/puma.rb but this is set to 16 and changing it makes no difference
Replies (7)
Hi Deryk,
For performance reasons we do not recommend to use less worker. When I got my first computer RAM was a big thing but in 2019?
Best
Niels
I see what you're saying but we're in a small business VM environment on a very limited budget and need to allocate RAM wisely... 4GB has been fine for every application we've thrown at our Linux VM so far whereas it's a push now, not really sure why OP has gone from taking up ~600-800MB in v9 to struggling to fit in 4GB in v10 just for the ability to drag and drop work packages :/
Got it, for anyone else wondering. The default number of workers was increased from 4 (in v9) to 28 (in v10)! Bit excessive for our needs.
Reconfigure with:
Deryk, thanks a lot!!! I have been trying to find the memory leak for two days! But, technically, there is no leak! Mine installation works smoothly with 8 workers, consuming less than 3 Gb in average (we are having like 20 users in total).
Thank you!
Hi guys,
could you chime in at #31201 with your distribution and set up to identify where this number is coming from? I'm still not sure where this value is coming from. We're not setting it actively but fallback if the ENV variable is not present.
Could you check in your
/etc/defaults,/etc/environmentor similar files depending on your setup ?Best,
Oliver
This is being backported to the packaged 10.0.2 release and is being built right now:
https://packager.io/gh/opf/openproject/refs/stable/10
It is renaming our use of the
WEB_CONCURRENCYvariable toOPENPROJECT_WEB_WORKERS.The bug was caused by the heroku buildpackage using the same variable for its internal setting, which is used by us only to install the nodejs environment. https://github.com/heroku/heroku-buildpack-nodejs/blob/5a76f5f19974424755789f82d14c1aa381434191/profile/WEB_CONCURRENCY.sh
Best,
Oliver
Docker and packaged installation was pushed, manual installation please just update the
stable/10branch and restart.Announcment of the release was extended with the details of this bug: https://www.openproject.org/release-notes/openproject-10-0-2/