incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <shadow...@gmail.com>
Subject RE: [DISCUSS] Management Server Memory Requirements
Date Thu, 21 Feb 2013 04:41:01 GMT
Thanks. Looks like test servers are 1GB. And there is swapping. Can you run
"vmstat 1" and give us 30 seconds of output?

So we need to decide as a dev team if we need to raise minimum requirements
and/or lower java process memory according to what new 4.1 code can get
away with.
On Feb 20, 2013 9:27 PM, "Sailaja Mada" <sailaja.mada@citrix.com> wrote:

> Hi,
>
> Cloudstack Java process statistics are given below when it stops
> responding are given below :
>
> top - 09:52:03 up 4 days, 21:43,  2 users,  load average: 0.06, 0.05, 0.02
> Tasks:   1 total,   0 running,   1 sleeping,   0 stopped,   0 zombie
> Cpu(s):  1.7%us,  0.7%sy,  0.0%ni, 97.3%id,  0.3%wa,  0.0%hi,  0.0%si,
>  0.0%st
> Mem:   1014860k total,   947632k used,    67228k free,     5868k buffers
> Swap:  2031608k total,   832320k used,  1199288k free,    26764k cached
>
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 12559 cloud     20   0 3159m 744m 4440 S  2.3 75.1   6:38.39 java
>
> Thanks,
> Sailaja.M
>
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: Thursday, February 21, 2013 9:35 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Management Server Memory Requirements
>
> Yes, these are great data points, but so far nobody has responded on that
> ticket with the information required to know if the slowness is related to
> memory settings or swapping. That was just a hunch on my part from being a
> system admin.
>
> How much memory do these systems have that experience issues? What does
> /proc/meminfo say during the issues? Does adjusting the tomcat6.conf memory
> settings make a difference (see ticket comments)? How much memory do the
> java processes list as resident in top?
> On Feb 20, 2013 8:53 PM, "Parth Jagirdar" <Parth.Jagirdar@citrix.com>
> wrote:
>
> > +1 Performance degradation is dramatic and I too have observed this
> issue.
> >
> > I have logged my comments into 1339.
> >
> >
> > ŠParth
> >
> > On 2/20/13 7:34 PM, "Srikanteswararao Talluri"
> > <srikanteswararao.talluri@citrix.com> wrote:
> >
> > >To add to what Marcus mentioned,
> > >Regarding bug CLOUDSTACK-1339 : I have observed this issue within
> > >5-10 min of starting management server and there has been a lot of
> > >API requests through automated tests. It is observed that Management
> > >server not only slows down but also goes down after a while.
> > >
> > >~Talluri
> > >
> > >-----Original Message-----
> > >From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> > >Sent: Thursday, February 21, 2013 7:22
> > >To: cloudstack-dev@incubator.apache.org
> > >Subject: [DISCUSS] Management Server Memory Requirements
> > >
> > >When Javelin was merged, there was an email sent out stating that
> > >devs should set their MAVEN_OPTS to use 2g of heap, and 512M of
> > >permanent memory.  Subsequently, there have also been several e-mails
> > >and issues where devs have echoed this recommendation, and presumably
> > >it fixed issues. I've seen the MS run out of memory myself and
> > >applied those recommendations.
> > >
> > >Is this what we want to provide in the tomcat config for a package
> > >based install as well? It's effectively saying that the minimum
> > >requirements for the management server are something like 3 or 4 GB
> > >(to be safe for other running tasks) of RAM, right?
> > >
> > >There is currently a bug filed that may or may not have to do with
> > >this, CLOUDSTACK-1339. Users report mgmt server slowness, going
> > >unresponsive for minutes at a time, but the logs seem to show
> > >business as usual. User reports that java is taking 75% of RAM,
> > >depending on what else is going on they may be swapping. Settings in
> > >the code for an install are currently at 2g/512M, I've been running
> > >this on a 4GB server for awhile now, java is at 900M, but I haven't
> > >been pounding it with requests or anything.
> > >
> > >This bug might not have anything to do with the memory settings, but
> > >I figured it would be good to nail down what our minimum requirements
> > >are for 4.1
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message