Open Stack

Hi Samuel,

I like the formula given here:

http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html

(0.5 * RAM) + (overcommit ratio * RAM) = Recommended swap size

This will ensure you never run out of swap space when overcommitting RAM --
which is imperative as described by the big red WARNING message in the
link.  :)

As far as I am aware, the other methods that KVM uses for memory management
(KSM and ballooning) are enabled and managed by default and shouldn't have
to be tweaked -- but someone please correct me if I am wrong.

Thanks,
Joe

On Fri, Sep 21, 2012 at 8:39 AM, Samuel Winchenbach <swinchen at gmail.com>wrote:

> Hi All,
>
> What are some "best practices" when it comes to overselling RAM in a
> KVM based openstack setup?  For example:
>
> I have 4 nodes with 16 cores & 128 GB RAM each.  If on one of those
> nodes I oversell ram 2:1 (256 GB RAM) and the VMs actually use that
> much does it just start swapping out pages to disk?
>
> How do all of you handle overselling RAM?
>
> Thanks,
> Sam
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Joe Topjian
Systems Administrator
Cybera Inc.

www.cybera.ca

Big data is coming to Canada. Join the welcome wagon.
*Cyber Summit 2012*
October 1-3, Banff
www.cybera.ca/summit2012

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120922/b81768d2/attachment.html>