From: David Gibson <david@gibson.dropbear.id.au>
To: Orit Wasserman <owasserm@redhat.com>
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] Testing migration under stress
Date: Mon, 5 Nov 2012 11:30:06 +1100 [thread overview]
Message-ID: <20121105003006.GW27695@truffula.fritz.box> (raw)
In-Reply-To: <5093B8A9.4060501@redhat.com>
On Fri, Nov 02, 2012 at 02:12:25PM +0200, Orit Wasserman wrote:
> On 11/02/2012 05:10 AM, David Gibson wrote:
> > Asking for some advice on the list.
> >
> > I have prorotype savevm and migration support ready for the pseries
> > machine. They seem to work under simple circumstances (idle guest).
> > To test them more extensively I've been attempting to perform live
> > migrations (just over tcp->localhost) which the guest is active with
> > something. In particular I've tried while using octave to do matrix
> > multiply (so exercising the FP unit) and my colleague Alexey has tried
> > during some video encoding.
> As you are doing local migration one option is to setting the speed
> higher than line speed , as we don't actually send the data, another
> is to set high downtime.
I'm not entirely sure what you mean by that. But I do have suspicions
based on this and other factors that the default bandwidth it is
limiting to is horribly, horribly low.
> > However, in each of these cases, we've found that the migration only
> > completes and the source instance only stops after the intensive
> > workload has (just) completed. What I surmise is happening is that
> > the workload is touching memory pages fast enough that the ram
> > migration code is never getting below the threshold to complete the
> > migration until the guest is idle again.
> >
> The workload you chose is really bad for live migration, as all the
> guest does is dirtying his memory.
Well, I realised that was true of the matrix multiply. For video
encode though, the output data should be much, much smaller than the
input, so I wouldn't expect it to be dirtying memory that fast.
> I recommend looking for workload
> that does some networking or disk IO. Vinod succeeded running
> SwingBench and SLOB benchmarks that converged ok, I don't know if
> they run on pseries, but similar workload should be ok(small
> database/warehouse). We found out that SpecJbb on the other hand is
> hard to converge. Web workload or video streaming also do the
> trick.
Hrm. As something really simple and stupid, I did try migrationg an
ls -lR /, but even that didn't converge :/.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-11-05 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 3:10 [Qemu-devel] Testing migration under stress David Gibson
2012-11-02 12:12 ` Orit Wasserman
2012-11-05 0:30 ` David Gibson [this message]
2012-11-05 12:21 ` Orit Wasserman
2012-11-06 1:14 ` David Gibson
2012-11-06 5:22 ` Alexey Kardashevskiy
2012-11-06 6:55 ` David Gibson
2012-11-06 7:55 ` Alexey Kardashevskiy
2012-11-06 10:54 ` Orit Wasserman
2012-11-02 13:04 ` Paolo Bonzini
2012-11-02 13:07 ` Juan Quintela
2012-11-05 0:31 ` David Gibson
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=20121105003006.GW27695@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).