Sure.

I tested in my local setup, you can actually use -Xmx512m settings to run
it. I'll look at the memory footprint issue together with the an
improvement effort to speed up management server startup time. With Spring
auto-component-scan turned on in a global scope, in a huge system like
CloudStack, it is just taking too long to start it up.

Kelven 

On 2/5/13 9:19 PM, "Alex Huang" <alex.hu...@citrix.com> wrote:

>Kelven,
>
>This needs to be a priority.  Spring with just aop and di shouldn't be
>that huge.  Something is wrong here.
>
>--Alex
>
>> -----Original Message-----
>> From: Kelven Yang [mailto:kelven.y...@citrix.com]
>> Sent: Monday, February 04, 2013 5:57 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [ACS41][QA]Issues observed with 4.1
>> 
>> Spring jars add up to make it cross the threshold line. I'm not sure how
>> much it has added, there are some tuning work to find a good number
>>here.
>> 
>> Kelven
>> 
>> 
>> On 2/4/13 5:42 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com>
>>wrote:
>> 
>> >Kelven, what is the reason for the huge increase in required memory?
>> >
>> >On 2/4/13 5:22 PM, "Kelven Yang" <kelven.y...@citrix.com> wrote:
>> >
>> >>The JVM memory setting I gave after Javelin merge may be too
>>aggressive
>> >>if
>> >>you are running management server inside a VM. -XX:MaxPermSize=512m
>> is
>> >>for
>> >>the fact that we have so many java classes (it might work in 256m
>> >>configuration I think) and -Xmx2g is for the total heap (2G), almost
>>the
>> >>maximum for a 32-bit process, if you are running inside a VM and don't
>> >>have much management server load, you may try out with 1G of heap
>>size.
>> >>
>> >>
>> >>Kelven
>> >>
>> >>On 2/4/13 3:44 PM, "Ryan Dietrich" <r...@betterservers.com> wrote:
>> >>
>> >>>Actually, the build reported success with no errors!   I ended up
>> >>>blowing
>> >>>away my entire cloudstack vm and started over.    Things seem to be
>> >>>working now.
>> >>>I actually run the management server ON devcloud itself, so the new
>> >>>memory requirements required me to up my settings (i.e.: export
>> >>>MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx2g")
>> >>>
>> >>>/boot/grub/grub.cfg
>> >>>
>> >>>I upped my xen "dom0_mem" so I could get a little more base memory.
>>I
>> >>>was swapping quite badly when trying to launch jetty, and got memory
>> >>>errors along the way.
>> >>>
>> >>>-Ryan Dietrich
>> >>>
>> >>>On Feb 4, 2013, at 3:00 PM, Kelven Yang <kelven.y...@citrix.com>
>>wrote:
>> >>>
>> >>>> It looks like your first command was actually failed to execute?
>> >>>> com.cloud.upgrade.DatabaseCreator is packaged in the artifact from
>> the
>> >>>> first command.
>> >>>>
>> >>>>
>> >>>> Kelven
>> >>>>
>> >>>>
>> >>>> On 2/4/13 9:20 AM, "Ryan Dietrich" <r...@betterservers.com> wrote:
>> >>>>
>> >>>>> After a pull on the master branch, I am unable to deploy the
>> >>>>>database.
>> >>>>>
>> >>>>> I ran:
>> >>>>>    mvn -P developer,systemvm clean install
>> >>>>> Then:
>> >>>>>    mvn -P developer -pl developer,tools/devcloud -Ddeploydb
>> >>>>> I got:
>> >>>>>    java.lang.ClassNotFoundException:
>> >>>>>com.cloud.upgrade.DatabaseCreator
>> >>>>>
>> >>>>>
>> >>>>> On Feb 4, 2013, at 9:40 AM, Sailaja Mada <sailaja.m...@citrix.com>
>> >>>>>wrote:
>> >>>>>
>> >>>>>> Hi,
>> >>>>>>
>> >>>>>> These are the observations with 4.1 master branch dev environment
>> >>>>>>today
>> >>>>>> .
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>

Reply via email to