cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Higginbottom <geoff.higginbot...@shapeblue.com>
Subject RE: CloudStack Server Memory Requirements
Date Mon, 30 Sep 2013 10:43:20 GMT
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.higginbottom@shapeblue.com

-----Original Message-----
From: Geoff Higginbottom [mailto:geoff.higginbottom@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.higginbottom@shapeblue.com

-----Original Message-----
From: Marcus Sorensen [mailto:shadowsor@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.Vittal@citrix.com> wrote:
> I believe Darren's proposed Spring refactor will help greatly.
>
> On 9/26/13 7:41 AM, "Marcus Sorensen" <shadowsor@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.higginbottom@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.

Mime
View raw message