From: Alan.Robinson@ts.fujitsu.com (Alan Robinson)
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: PV performance degraded after live migration
Date: Wed, 15 Mar 2017 16:43:52 +0100 [thread overview]
Message-ID: <20170315154352.GA10717@ts.fujitsu.com> (raw)
In-Reply-To: <20170315112044.GA14366@aepfle.de>
Hi Olaf,
On Wed, Mar 15, 2017 at 12:20:44PM +0100, Olaf Hering wrote:
> After reports about degraded performance after a PV domU was migrated
> from one dom0 to another it turned out that this issue happens with
> every version of Xen and every version of domU kernel.
>
> The used benchmark is 'sysbench memory'. I hacked it up to show how long
> the actual work takes, and that loop takes longer to execute after the
> domU is migrated. In my testing the loop (memory_execute_event) takes
> about 1200ns, after migration it takes about 1500ns. It just writes 0 to
> an array of memory. In total sysbench reports 6500 MiB/sec, after
> migration its just 3350 MiB/sec.
We have seen something similar being caused by the superpage
attribute getting dropped when the domU was migrated. The new
copy of the domU only has 4K pages instead of 2MB pages eventually
this would seem to fit your memory access sysbench results.
Alan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-15 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 11:20 PV performance degraded after live migration Olaf Hering
2017-03-15 11:30 ` Andrew Cooper
2017-03-15 14:52 ` Olaf Hering
2017-03-15 15:23 ` Olaf Hering
2017-03-15 15:26 ` Andrew Cooper
2017-03-15 15:33 ` Juergen Gross
2017-03-15 15:43 ` Boris Ostrovsky
2017-03-15 15:53 ` Juergen Gross
2017-03-15 16:13 ` Jan Beulich
2017-03-16 8:13 ` Olaf Hering
2017-03-16 10:20 ` Jan Beulich
2017-03-15 16:02 ` Jan Beulich
2017-03-15 16:41 ` Boris Ostrovsky
2017-03-15 16:50 ` Jan Beulich
2017-03-15 15:43 ` Alan Robinson [this message]
2017-03-15 15:51 ` Andrew Cooper
2017-03-15 15:53 ` Jan Beulich
2017-03-15 15:56 ` Alan Robinson
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=20170315154352.GA10717@ts.fujitsu.com \
--to=alan.robinson@ts.fujitsu.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.