CloudStack should start and run for a small setup fine with a 256m heap. Obviously you should probably run with more in a production setup. I'm running the following opts on centos6.4
JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=128m -XX:MaxPermSize=256m" That puts the resident memory around 600mb. This is obviously a very minimal setup, if I was to put much load on it the GC would probably thrash the CPU. Darren On Tue, Oct 1, 2013 at 2:48 AM, Geoff Higginbottom <geoff.higginbot...@shapeblue.com> wrote: > Marcus, > > Thanks for the pointer. > > After some experimentation, I was able to get the system to function with 1GB > or RAM, but no less. > > I changed the -XX:PermSize / -XX:MaxPermSize settings from 512 / 800 to 256 / > 512. > > ORIGINAL > JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false -Xmx2g > -XX:+HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M > -XX:MaxPermSize=800m" > > NEW > JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false -Xmx2g > -XX:+HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=256M > -XX:MaxPermSize=512m" > > I was actually able to drop these values lower, but the CSMAN VM still needs > 1GB of RAM regardless so something else must be hogging the RAM. > > Whilst this now works with a 1GB Memory Allowance for the CloudStack > Management Server, it is still x2 what CloudStack 4.1 needed. > > For building test environments on a Laptop in Virtual Box with a separate > Host VM such as XenServer 6.2, every MB of RAM is critical. Fortunately I > have lots of real hardware at my disposal but not everyone does hence my > quest to be able to build a test environment on a Latptop with only 4GB of > RAM. > > If anyone on the DEV List has any ideas how we can get CloudStack 4.2 to run > on 512 MB of RAM like 4.1 did I would be happy to test their theories. > > Regards > > Geoff Higginbottom > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 > > geoff.higginbot...@shapeblue.com > > -----Original Message----- > From: Marcus Sorensen [mailto:shadow...@gmail.com] > Sent: 30 September 2013 16:17 > To: Geoff Higginbottom > Cc: chiradeep.vit...@citrix.com; dev@cloudstack.apache.org > Subject: Re: CloudStack Server Memory Requirements > > Edit JAVA_OPTS in /etc/cloudstack/management/tomcat6.conf (or whatever file > your system uses) and adjust the memory settings as desired. > > On Mon, Sep 30, 2013 at 4:43 AM, Geoff Higginbottom > <geoff.higginbot...@shapeblue.com> wrote: >> Marcus, Chiradeep, >> >> You've both made reference to the 'Spring Refactor', any chance you can let >> me know how I go about changing this so I can run CloudStack on a 1GB (or >> less) foot print, rather than the current 2GB. >> >> Regards >> >> Geoff Higginbottom >> >> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 >> >> geoff.higginbot...@shapeblue.com >> >> -----Original Message----- >> From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com] >> Sent: 27 September 2013 08:57 >> To: dev@cloudstack.apache.org >> Subject: RE: CloudStack Server Memory Requirements >> >> All, >> >> Thanks for all the replies, now a simple question, what do I need to change >> to test it? >> >> Regards >> >> Geoff Higginbottom >> >> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 >> >> geoff.higginbot...@shapeblue.com >> >> -----Original Message----- >> From: Marcus Sorensen [mailto:shadow...@gmail.com] >> Sent: 26 September 2013 20:29 >> To: dev@cloudstack.apache.org >> Subject: Re: CloudStack Server Memory Requirements >> >> If I recall, we were able to start running it in devcloud again with only 1G >> of memory allocated to dom0 just a few weeks after the initial spring merge. >> I just think the default was never set back. >> >> On Thu, Sep 26, 2013 at 11:29 AM, Chiradeep Vittal >> <chiradeep.vit...@citrix.com> wrote: >>> I believe Darren's proposed Spring refactor will help greatly. >>> >>> On 9/26/13 7:41 AM, "Marcus Sorensen" <shadow...@gmail.com> wrote: >>> >>>>I think its an artifact from the Spring stuff six months ago. We can >>>>probably decrease that in the default tomcat conf now. >>>>On Sep 26, 2013 6:11 AM, "Geoff Higginbottom" < >>>>geoff.higginbot...@shapeblue.com> wrote: >>>> >>>>> I¹ve been testing the 4.2 release of CloudStack using Virtual Box >>>>> and have noticed a need to allocate significantly more memory to the VM. >>>>> Previously I would use a CentOS VM with 1 GB of RAM for the >>>>> installation but then drop the memory to 512MB, leaving plenty of >>>>> RAM on the host machine to then stand up a XenServer VM or a KVM VM etc. >>>>> >>>>> >>>>> >>>>> I initially had problems logging into 4.2 after a clean install, >>>>>and discovered that only by increasing the memory to 2GB could I get >>>>>the system to function. >>>>> >>>>> >>>>> >>>>> I am quite shocked that the memory footprint has increased 400% >>>>>between releases. Obviously for a real production system, >>>>>allocating more than 2GB or RAM to CloudStack is not an issue, but >>>>>it does make standing up a simple test environment in Virtual Box >>>>>more difficult. >>>>> >>>>> >>>>> >>>>> Does anyone have ideas why this has increased and is it something >>>>> that should be looked at. >>>>> >>>>> >>>>> >>>>> Regards >>>>> >>>>> >>>>> >>>>> Geoff Higginbottom >>>>> >>>>> *CTO / Cloud Architect* >> This email and any attachments to it may be confidential and are intended >> solely for the use of the individual to whom it is addressed. Any views or >> opinions expressed are solely those of the author and do not necessarily >> represent those of Shape Blue Ltd or related companies. If you are not the >> intended recipient of this email, you must neither take any action based >> upon its contents, nor copy or show it to anyone. Please contact the sender >> if you believe you have received this email in error. Shape Blue Ltd is a >> company incorporated in England & Wales. ShapeBlue Services India LLP is a >> company incorporated in India and is operated under license from Shape Blue >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil >> and is operated under license from Shape Blue Ltd. ShapeBlue is a registered >> trademark. > This email and any attachments to it may be confidential and are intended > solely for the use of the individual to whom it is addressed. Any views or > opinions expressed are solely those of the author and do not necessarily > represent those of Shape Blue Ltd or related companies. If you are not the > intended recipient of this email, you must neither take any action based upon > its contents, nor copy or show it to anyone. Please contact the sender if you > believe you have received this email in error. Shape Blue Ltd is a company > incorporated in England & Wales. ShapeBlue Services India LLP is a company > incorporated in India and is operated under license from Shape Blue Ltd. > Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is > operated under license from Shape Blue Ltd. ShapeBlue is a registered > trademark.
