Adding '-Xmx1124M' should work by adding into the init script
somewhere. I am not sure if the Cloudstack Agent would care about this
however, probably worth a try on something that isn't important :P

Marty

On 26 April 2014 14:36, Andrija Panic <andrija.pa...@gmail.com> wrote:
> Is there any way to hack and limit RAM consumtion, java heap size, etc. ?
> After 24h uptime, cloudstack-agent daemin is again 5GB on one of the
> servers...
> Thanks
>
>
> On 25 April 2014 22:28, Andrija Panic <andrija.pa...@gmail.com> wrote:
>
>> I'm on CentOS 6.5 x64...very interesting size... BTW main
>> cloudstack-management process is much less in size...strange to see agent
>> so big...
>>
>>
>> On 25 April 2014 19:55, Marty Sweet <msweet....@gmail.com> wrote:
>>
>>> This is interesting, what OS do you have them running on?
>>>
>>> This is the first time I have looked at this, I am running Ubuntu
>>> 12.04.4 x64 with CS4.2.0.
>>>
>>> ==
>>>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>>> 41874 root      20   0 63.8g  58g 6952 S  134 23.3 501156:53 kvm
>>> 24987 root      20   0 6862m 6.0g 6960 S   56  2.4  17283:27 kvm
>>> 65308 root      20   0 8870m 4.1g 6916 S   22  1.6  65734:54 kvm
>>> 47506 root      20   0 7032m 4.0g 6908 S   14  1.6  36832:54 kvm
>>>  1737 root      20   0 8608m 4.1g 6948 S    2  1.6   2436:28 kvm
>>> 28310 root      20   0 46.5g  11g  17m S    1  4.4   1650:01 jsvc
>>> 28309 root      20   0 10656  412  292 S    0  0.0   0:06.54 jsvc
>>> 28307 root      20   0 10656  296  204 S    0  0.0   0:00.00 jsvc
>>>
>>> ==
>>> root@aurora:~# free -g
>>>              total       used       free     shared    buffers     cached
>>> Mem:           251        245          6          0          0        156
>>> -/+ buffers/cache:         88        163
>>> Swap:            5          0          4
>>> ==
>>>
>>> So I currently am "using" 88GB on this host, which approx
>>> (58+6+4+4+4+11). It's intresting why the jsvc for the Cloudstack
>>> Hypervisor agent would require 11GB of RAM.
>>>
>>> Usage vs. Uptime
>>> 178 days = 10G
>>> 179 days = 14G
>>> 179 days = 11G
>>> 51 days   = 5.2G
>>>
>>> Do we need to be limiting the Java heap size?
>>>
>>> Marty
>>>
>>> On 25 April 2014 18:07, Andrija Panic <andrija.pa...@gmail.com> wrote:
>>> > Ok, my bad. It is cloudstack-agent daemon on physical host. installed
>>> from
>>> > official CS repo.
>>> > thanks
>>> > On Apr 25, 2014 5:36 PM, "Michael Phillips" <mphilli7...@hotmail.com>
>>> wrote:
>>> >
>>> >> Curious as to what agent you are referring to. the cloud agent
>>> installed
>>> >> on the vm's, the system vm's etc...
>>> >>
>>> >> > Date: Fri, 25 Apr 2014 17:34:12 +0200
>>> >> > Subject: Re: Agent excesive RAM usage...
>>> >> > From: andrija.pa...@gmail.com
>>> >> > To: users@cloudstack.apache.org
>>> >> >
>>> >> > ah sorry, 4.2.1... (was upgrade from 4.0.0 I think...)
>>> >> >
>>> >> > Best,
>>> >> >
>>> >> >
>>> >> > On 25 April 2014 17:30, Michael Phillips <mphilli7...@hotmail.com>
>>> >> wrote:
>>> >> >
>>> >> > > What agent are you referring to?
>>> >> > >
>>> >> > > > Date: Fri, 25 Apr 2014 17:28:44 +0200
>>> >> > > > Subject: Agent excesive RAM usage...
>>> >> > > > From: andrija.pa...@gmail.com
>>> >> > > > To: users@cloudstack.apache.org
>>> >> > > >
>>> >> > > > Hi,
>>> >> > > >
>>> >> > > > I just noticed that I had cloudstack agent taking over 9GB on one
>>> >> > > servers,
>>> >> > > > and over 5GB on others...
>>> >> > > >
>>> >> > > > Is there a know bug or something ?
>>> >> > > >
>>> >> > > > Thanks,
>>> >> > > >
>>> >> > > > --
>>> >> > > >
>>> >> > > > Andrija Panić
>>> >> > >
>>> >> > >
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> >
>>> >> > Andrija Panić
>>> >> > --------------------------------------
>>> >> >   http://admintweets.com
>>> >> > --------------------------------------
>>> >>
>>>
>>
>>
>>
>> --
>>
>> Andrija Panić
>> --------------------------------------
>>   http://admintweets.com
>> --------------------------------------
>>
>
>
>
> --
>
> Andrija Panić
> --------------------------------------
>   http://admintweets.com
> --------------------------------------

Reply via email to