You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Rene Moser <ma...@renemoser.net> on 2018/09/18 15:56:05 UTC
VRs swapping with 256 MB RAM
Hi
While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
critical because the management server connections to VRs took very
long, minutes, this resulted in many more problems all over.
Make sure your VRs have enough RAM.
Regards
René
Re: VRs swapping with 256 MB RAM
Posted by Rene Moser <ma...@renemoser.net>.
Hi
Just to clarify, we had 256 MB in our lab only.
The prod VRs have 1 GB RAM and 4 CPUs, 1 CPU per network interface for
optimal performance + 1 for the OS.
Regards
René
On 09/20/2018 02:35 PM, Rakesh Venkatesh wrote:
> Hello Rene
>
> Even for VR's running on KVM, 256MB is really less. Thats why we offer
> extra VR with 2 cores and 1GB RAM as another option so that customers can
> use it instead of the default 256MB and 1 core.
>
> On Tue, Sep 18, 2018 at 5:56 PM Rene Moser <ma...@renemoser.net> wrote:
>
>> Hi
>>
>> While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
>> low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
>> critical because the management server connections to VRs took very
>> long, minutes, this resulted in many more problems all over.
>>
>> Make sure your VRs have enough RAM.
>>
>> Regards
>> René
>>
>
>
Re: VRs swapping with 256 MB RAM
Posted by Rene Moser <ma...@renemoser.net>.
Hi
Just to clarify, we had 256 MB in our lab only.
The prod VRs have 1 GB RAM and 4 CPUs, 1 CPU per network interface for
optimal performance + 1 for the OS.
Regards
René
On 09/20/2018 02:35 PM, Rakesh Venkatesh wrote:
> Hello Rene
>
> Even for VR's running on KVM, 256MB is really less. Thats why we offer
> extra VR with 2 cores and 1GB RAM as another option so that customers can
> use it instead of the default 256MB and 1 core.
>
> On Tue, Sep 18, 2018 at 5:56 PM Rene Moser <ma...@renemoser.net> wrote:
>
>> Hi
>>
>> While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
>> low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
>> critical because the management server connections to VRs took very
>> long, minutes, this resulted in many more problems all over.
>>
>> Make sure your VRs have enough RAM.
>>
>> Regards
>> René
>>
>
>
Re: VRs swapping with 256 MB RAM
Posted by Rakesh Venkatesh <ww...@gmail.com>.
Hello Rene
Even for VR's running on KVM, 256MB is really less. Thats why we offer
extra VR with 2 cores and 1GB RAM as another option so that customers can
use it instead of the default 256MB and 1 core.
On Tue, Sep 18, 2018 at 5:56 PM Rene Moser <ma...@renemoser.net> wrote:
> Hi
>
> While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
> low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
> critical because the management server connections to VRs took very
> long, minutes, this resulted in many more problems all over.
>
> Make sure your VRs have enough RAM.
>
> Regards
> René
>
--
Thanks and regards
Rakesh venkatesh
Re: VRs swapping with 256 MB RAM
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi Rene,
I've come across issues where vmware side would provision less than 256MB RAM to the guest OS while vCenter would still claim to have reserved/allocated 256MB RAM. I've seen this happen few cases, which is why for 4.11+ VRs on vmware the guest os type selected is 'other linux 64'. Reference:
https://github.com/apache/cloudstack/blob/master/engine/schema/src/main/resources/META-INF/db/schema-41000to41100.sql#L448
Can you share what RAM allocation you see from vCenter side and inside of the VR by sharing the 'free -m' output from the VR?
While one can always increase the cpu/memory limits for default system offerings, the default of 256MB RAM should ideally work (at least works on kvm, xenserver). If we can conclude this behaviour, we can consider increasing the default VR RAM by 64 or 128MB, i.e. to 320 or 384 MB by default.
- Rohit
<https://cloudstack.apache.org>
________________________________
From: Rene Moser <ma...@renemoser.net>
Sent: Tuesday, September 18, 2018 9:26:05 PM
To: dev@cloudstack.apache.org; users@cloudstack.apache.org
Subject: VRs swapping with 256 MB RAM
Hi
While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
critical because the management server connections to VRs took very
long, minutes, this resulted in many more problems all over.
Make sure your VRs have enough RAM.
Regards
René
rohit.yadav@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
Re: VRs swapping with 256 MB RAM
Posted by Rakesh Venkatesh <ww...@gmail.com>.
Hello Rene
Even for VR's running on KVM, 256MB is really less. Thats why we offer
extra VR with 2 cores and 1GB RAM as another option so that customers can
use it instead of the default 256MB and 1 core.
On Tue, Sep 18, 2018 at 5:56 PM Rene Moser <ma...@renemoser.net> wrote:
> Hi
>
> While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
> low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
> critical because the management server connections to VRs took very
> long, minutes, this resulted in many more problems all over.
>
> Make sure your VRs have enough RAM.
>
> Regards
> René
>
--
Thanks and regards
Rakesh venkatesh
Re: VRs swapping with 256 MB RAM
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi Rene,
I've come across issues where vmware side would provision less than 256MB RAM to the guest OS while vCenter would still claim to have reserved/allocated 256MB RAM. I've seen this happen few cases, which is why for 4.11+ VRs on vmware the guest os type selected is 'other linux 64'. Reference:
https://github.com/apache/cloudstack/blob/master/engine/schema/src/main/resources/META-INF/db/schema-41000to41100.sql#L448
Can you share what RAM allocation you see from vCenter side and inside of the VR by sharing the 'free -m' output from the VR?
While one can always increase the cpu/memory limits for default system offerings, the default of 256MB RAM should ideally work (at least works on kvm, xenserver). If we can conclude this behaviour, we can consider increasing the default VR RAM by 64 or 128MB, i.e. to 320 or 384 MB by default.
- Rohit
<https://cloudstack.apache.org>
________________________________
From: Rene Moser <ma...@renemoser.net>
Sent: Tuesday, September 18, 2018 9:26:05 PM
To: dev@cloudstack.apache.org; users@cloudstack.apache.org
Subject: VRs swapping with 256 MB RAM
Hi
While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
critical because the management server connections to VRs took very
long, minutes, this resulted in many more problems all over.
Make sure your VRs have enough RAM.
Regards
René
rohit.yadav@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue