qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] slow migration speed / strange memory usage
Date: Mon, 29 Oct 2012 11:44:37 +0100	[thread overview]
Message-ID: <508E5E15.9060302@profihost.ag> (raw)

Hello list,

i'm running kvm 1.2 on vanilla 3.6.3 kernel.

I'm trying to understand the memory usage and the migration speed.

I've a VM which does nothing else than running OpenSSH and a cron job 
every minute to write a small json file.

When the VM is freshly started Host shows 300MB memory usage and 
migration speed is around 400MB/s.

After time the memory usage increases in up to 3.7GB but in VM it stays 
incl. cache and buffers around 350MB.

The migration speed is then around 25MB/s.

How can this be? Is this expected? Disk cache is set to default (no cache).

Greets,
Stefan

                 reply	other threads:[~2012-10-29 10:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=508E5E15.9060302@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=qemu-devel@nongnu.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).