From: Avi Kivity <avi@redhat.com>
To: dbareiro@gmx.net, KVM General <kvm@vger.kernel.org>
Subject: Re: Very high memory usage with KVM
Date: Sun, 09 Aug 2009 12:12:43 +0300 [thread overview]
Message-ID: <4A7E930B.6030803@redhat.com> (raw)
In-Reply-To: <20090808005428.GB6072@defiant.freesoftware.org>
On 08/08/2009 03:54 AM, Daniel Bareiro wrote:
>> My guess is that it is due to poor swapping with pre-2.6.27 hosts.
>> 15 GB used out of 16GB total is just 6% reserve, which may be a bit
>> too low. With a 2.6.27 host some small amount of memory would be
>> swapped out, before that you'd see thrashing. Another way to check
>> is to drop one guest (or reduce total memory needed by 1GB) and see
>> if you get the same results or if things improve.
>>
>
> I was testing in another equipment of similar characteristics with 4 VMs of
> 3.5 GiB of RAM on LVM and rather less the 16 GB of RAM in use in the host
> machine and 4 GIB available of the 8 GIB of swap, and after to update to
> KVM-88 the use of virtual memory improved enough.
>
> At the moment these are the statistics of memory usage:
>
> root@ss03:~# free
> total used free shared buffers cached
> Mem: 16463396 6700900 9762496 0 2805756 391884
> -/+ buffers/cache: 3503260 12960136
> Swap: 8319948 0 8319948
>
>
> Still I didn't update the kernel, so I am using KVM-88 with kernel
> 2.6.24-19. I would like to know if this can have some disadvantage, since
> in the official site of the project I was reading that kernel has to be
> 2.6.25 or newer to run the kvm 76 userspace (or any newer release).
>
I think it's just luck; with kernel < 2.6.27 swapping behaviour will not
be very good.
> The reason by which I didn't update kernel is because I was with some
> problems with the network interface on the host machine. Perhaps this
> problem is off-topic, but if somebody can help me with this, then it would
> contribute whereupon it can improve the KVM performance.
>
>
Please take it to netdev, perhaps they can help you with this.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-09 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 17:43 Very high memory usage with KVM Daniel Bareiro
2009-07-26 11:31 ` Avi Kivity
2009-07-26 14:56 ` Daniel Bareiro
2009-07-26 15:11 ` Avi Kivity
2009-07-26 15:50 ` Daniel Bareiro
2009-07-26 16:19 ` Avi Kivity
2009-08-08 0:54 ` Daniel Bareiro
2009-08-09 9:12 ` Avi Kivity [this message]
2009-08-10 6:40 ` Bernhard Held
2009-08-10 15:22 ` Daniel Bareiro
2009-08-10 16:15 ` Bernhard Held
2009-08-22 2:28 ` Daniel Bareiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A7E930B.6030803@redhat.com \
--to=avi@redhat.com \
--cc=dbareiro@gmx.net \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).