On Thu, Jan 12, 2012 at 11:36 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 01/12/2012 11:27 AM, Jonathan Petersson wrote: >> Hi, >> >> Throughout the last few months we've been slowly migrating off our old >> VMware installation to KVM, most of it has been successful and people >> has been happy with the end-result. >> >> The new infrastructure obviously has a bit more of power which is >> heavily utilized by the guests however compared to VMware the RAM >> usage is way above what we've expected. >> >> In our VMware environment we operated at 24GB with ballooning and we >> were able to maintain usage at around 90% without any swapping. >> However with the new environment we've 24x3 GB och RAM and we're >> seeing a 80% utilization across the board with the same amount of >> guests. >> >> Please notice that we've both ballooning (on both the host and guest) >> and KSM enabled, hugepages hasn't made any major difference so we've >> chosen to disable this. If you've any input as to why we're seeing >> this behavior or if it's expected we'd appreciate it. In addition to >> this we're utilizing virtio_blk/net/pci/ring and vhost_net. >> >> Some data: >> root@kvm01-01:~# grep -i balloon /boot/config-$(uname -r) >> CONFIG_VMWARE_BALLOON=m >> CONFIG_XEN_BALLOON=y >> CONFIG_VIRTIO_BALLOON=y >> > > What's the aggregate size of the guests (sum of all guest memory > sizes)? How many guests? Are you in fact using the balloon? How? > > -- > error compiling committee.c: too many arguments to function > This is a sample from one of the servers: Aggregate size is 28672 MB wheras 20133 is utilized on the host. Looking at each induvidual VM the actual utilization is rarely above 20% i.e. ~ 6GB. On this particular host there's a total of 23 VMs. Each VM is started with -balloon virtio, the host and the guests has the virtio_balloon drivers loaded. -- Jonathan Petersson - Operations Engineer op5 AB Norgegatan 2 SE-164 32 Kista, Sweden Direct +46 8-58 83 01 21 Mob +46 733709021 E-mail: jpetersson@xxxxxxx www.op5.com -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
