Load not being distributed

6 views

Skip to first unread message

Patrick Gibson

unread,

May 19, 2016, 1:04:32 PM5/19/16

to Phusion Passenger Discussions

For some reason, it seems like only a handful of available app instances are serving requests, and the primary one is ballooning in memory size. We're still on 5.0.20, so I will try upgrading to the latest, but this still seems odd to me. Any thoughts? (Running under Nginx on FreeBSD 10.)

* PID: 16903 Sessions: 1 Processed: 1549 Uptime: 27m 37s

CPU: 24% Memory : 5001M Last used: 1s ago

* PID: 16908 Sessions: 0 Processed: 614 Uptime: 27m 37s

CPU: 6% Memory : 1788M Last used: 0s ago

* PID: 16913 Sessions: 0 Processed: 133 Uptime: 27m 37s

CPU: 1% Memory : 635M Last used: 11s ago

* PID: 16918 Sessions: 0 Processed: 27 Uptime: 27m 37s

CPU: 0% Memory : 330M Last used: 3m 53s ago

* PID: 16923 Sessions: 0 Processed: 12 Uptime: 27m 36s

CPU: 0% Memory : 243M Last used: 8m 58s ago

* PID: 16928 Sessions: 0 Processed: 3 Uptime: 27m 36s

CPU: 0% Memory : 253M Last used: 16m 59s ago

* PID: 16933 Sessions: 0 Processed: 5 Uptime: 27m 36s

CPU: 0% Memory : 218M Last used: 16m 59s ago

* PID: 16938 Sessions: 0 Processed: 1 Uptime: 27m 35s

CPU: 0% Memory : 229M Last used: 27m 35s ago

* PID: 16943 Sessions: 0 Processed: 0 Uptime: 27m 35s

CPU: 0% Memory : 211M Last used: 27m 35s ago

* PID: 16948 Sessions: 0 Processed: 0 Uptime: 27m 35s

CPU: 0% Memory : 211M Last used: 27m 35s ago

* PID: 16953 Sessions: 0 Processed: 0 Uptime: 27m 35s

CPU: 0% Memory : 211M Last used: 27m 35s ago

* PID: 16958 Sessions: 0 Processed: 0 Uptime: 27m 34s

CPU: 0% Memory : 211M Last used: 27m 34s ago

* PID: 16965 Sessions: 0 Processed: 0 Uptime: 27m 34s

CPU: 0% Memory : 211M Last used: 27m 34s ago

Daniel Knoppel

unread,

May 19, 2016, 7:37:16 PM5/19/16

to Phusion Passenger Discussions

Looks normal to me. The load is distributed top down for caching efficiency and to facilitate autoscaling (being able to spin down processes that are not needed). Apparently the first 8 processes are enough to handle the load you are receiving (about 85 requests per minute).

In version 5.0.26 and up you can get extra load statistics (passenger-status --show=server).