[chef] Re: Re: Re: Re: Re: chef-client memory usage

[Bryan Berry < >]

sadly, cgroups are only available on centos 6

I run chef-client under a cron job rather than under a daemon, that
will reduce memory usage over time but not protect you from spikes.

I don't know if ruby's vm take gc tuning options like java but that could help

On Tue, Dec 20, 2011 at 8:29 PM, Chris 
<
 >
 wrote:
> Yeah, I wouldn't call centos 5.5 modern, I'll have to look and see if we 
> can even support cgroups
>
> Sent from a phone
>
>
> On Dec 20, 2011, at 8:56 AM, Sean OMeara 
> <
 >
>  wrote:
>
>> I haven't actually had a chance to play with these myself, but if
>> you're on a modern linux distro, you may be able to use cgroups to
>> isolate memory usage on a per process basis. (ie, keep your Java
>> processes safe)
>>
>> http://en.wikipedia.org/wiki/Cgroups
>> http://northernmost.org/blog/control-groups-in-rhel6/
>>
>> -s
>>
>> On Mon, Dec 12, 2011 at 8:32 PM, Chris 
>> <
 >
>>  wrote:
>>> That's not a bad idea either, we already have monit running on each 
>>> client node to restart the client when it crashes
>>>
>>> Sent from a phone
>>>
>>>
>>> On Dec 12, 2011, at 4:34 PM, Brian Akins 
>>> <
 >
>>>  wrote:
>>>
>>>>
>>>> On Dec 9, 2011, at 11:58 AM, Chris wrote:
>>>>
>>>>> Yep, that worked. Thanks.
>>>>>
>>>>> Client is sitting at 138m RSS now, which is a lot better. Hopefully it 
>>>>> will stop creeping up over time as well.
>>>>
>>>> Lately, we've been running monit (for various services) and we have it 
>>>> restart chef-client when memory is above x MB for n minutes.
>>>>
>>>> --Brian