We wish to narrow it down, there is no top, passenger will eventually
restart the processes automatically. If you want to dig try https://github.com/lzap/foreman-tracer
LZ
···
On Thu, Jan 26, 2017 at 9:30 AM, Matt . wrote:
> Hi,
>
> I have seen some huge memory usage for Passenger on a system that has
> a lot of hosts but is not queried a lot.
>
> Can we narrow this down ? I think 1G max should be OK.
>
> 48.3242 MB dynflow_executor_monitor
> 187.027 MB dynflow_executor
> 190.691 MB Passenger
> 205.309 MB Passenger
> 350.852 MB /usr/bin/java
> 1234.53 MB /usr/bin/java
> 2031.67 MB Passenger
> 2036.85 MB Passenger
>
> Day later:
>
>
> 231.945 MB dynflow_executor
> 412.824 MB /usr/bin/java
> 519.164 MB Passenger
> 1673.5 MB /usr/bin/java
>
> Thanks,
>
> Matt
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
