From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: "Xen-Devel (xen-devel@lists.xensource.com)"
<xen-devel@lists.xensource.com>
Subject: RE: Writing to a ramdisk in a PV domain is SLLLOOOWWW?!?
Date: Wed, 5 May 2010 13:16:31 -0700 (PDT) [thread overview]
Message-ID: <dc7b9ca4-a489-4fa2-8ddc-048dbedcbee7@default> (raw)
In-Reply-To: <89f1cead-b77d-4294-ab12-5e05344ed346@default>
It appears that ramswap is bad for HV domains also.
On one run:
real 11m38.017s
user 0m6.696s
sys 0m27.865s
I tried on bare-metal Linux and there is a
similar pattern but not nearly as bad:
real 0m54.978s
user 0m8.577s
sys 0m3.094s
Maybe there is some horrible TLB thrashing going
on even on bare-metal that is made even worse by
virtualization?
> -----Original Message-----
> From: Dan Magenheimer
> Sent: Wednesday, May 05, 2010 12:14 PM
> To: Xen-Devel (xen-devel@lists.xensource.com)
> Subject: Writing to a ramdisk in a PV domain is SLLLOOOWWW?!?
>
> Has anyone tried using a ramdisk in a PV domain?
>
> I'm trying it in an experiment to compare swapping to
> a ramdisk against tmem (frontswap) performance
> (suggested as a performance test on lkml).
>
> Writing to the ramdisk appears to be VERY VERY slow,
> elapsed time in the guest is several times larger than
> user+sys, and xentop shows the guest consuming vcpu
> seconds at about the user+sys rate. Note that
> this is when tmem is turned off and there is no
> vhd swap disk configured.
>
> I'm suspecting that writing to ramdisk must be causing
> some interesting/expensive PV pagetable behavior?
> Or maybe somehow /dev/ram0 is getting routed through
> qemu? Or ??
>
> Thanks,
> Dan
>
> P.S. Yes, I realize a ramdisk has no real value in
> a guest... this is just a performance experiment.
next prev parent reply other threads:[~2010-05-05 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 18:14 Writing to a ramdisk in a PV domain is SLLLOOOWWW?!? Dan Magenheimer
2010-05-05 20:16 ` Dan Magenheimer [this message]
2010-05-06 17:42 ` Jeremy Fitzhardinge
2010-05-06 21:02 ` Dan Magenheimer
2010-05-06 22:04 ` Santos, Jose Renato G
2010-05-06 22:26 ` Jeremy Fitzhardinge
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=dc7b9ca4-a489-4fa2-8ddc-048dbedcbee7@default \
--to=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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 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.