My account is limited to 300 process. As I turn on my rail app it ate up 100ps. Does anyone know how to reduce "Passenger Core" and PassengerAgent count? This is my nginx config:
This is output of the ps list: http://pastebin.com/0DcrmxC4 Thanks asked 23 Feb '17, 20:36 bliz20 |
Unfortunately, this is the default behavior for Passenger. It spawns a certain number of threads per CPU core on the server, and your server has 40 CPU cores, so it means a lot of threads are spawned. The thread count can't be adjusted on the free version of Passenger that our installer uses, so if the high number of threads is causing you to bump up against the thread limit, then you can try deploying with a custom server stack, perhaps with Puma. You can install Puma with the following commands:
Next, edit your project's
Then, stop your Nginx server:
Then, start Puma on your app's assigned port (eg 12345):
In my testing, the Puma process used only 18 threads. I hope this helps! Please let us know if you need anything else. answered 24 Feb '17, 23:22 seanf Thanks, let me give this a try.
(27 Feb '17, 15:48)
bliz20
|
The configuration options are outlined here. Some debugging will have to show what those processes are, but it is possible they are open files. answered 23 Feb '17, 22:23 johns I captured the process list after restart and once more after a few hours the result look similar.
(24 Feb '17, 13:49)
bliz20
|