All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Vrable <mvrable@cs.ucsd.edu>
To: Xen-devel@lists.sourceforge.net
Subject: Re: Copy-on-write memory to allow many more xenU domains per machine
Date: Tue, 26 Oct 2004 15:19:55 -0700	[thread overview]
Message-ID: <20041026151955.B25506@cs.ucsd.edu> (raw)
In-Reply-To: <E1CMXEA-000212-00@mta1.cl.cam.ac.uk>; from Ian.Pratt@cl.cam.ac.uk on Tue, Oct 26, 2004 at 08:43:30PM +0100

On Tue, Oct 26, 2004 at 08:43:30PM +0100, Ian Pratt wrote:
> > "Memory Resource Management in VMware ESX Server" by Carl Waldspurger
> > has some numbers on memory sharing between VMs:
> >     http://www.usenix.org/events/osdi02/tech/waldspurger/waldspurger.pdf
> > (This paper is also cited in the Xen SOSP 2003 paper.)
> > 
> > Sharing between identical machines is good, though sharing between
> > dissimilar machines is not as high as I remembered (copy-on-write
> > sharing is able to save around 7-30% of memory in real-world testing).
> 
> As I recall, Carl's results were on Windows, which might explain
> why I was seeing rather less. Linux resident set sizes tend to be
> smaller, and there's generally rather more diversity in the
> install base (at least around here).

Both were tested in that paper; Windows was at the high end of the scale
and Linux at the low end:

Reproducing Figure 5 from the paper in slightly abbreviated form:

          Guests        % Shared        % Reclaimed
        10 x WinNT        42.9              32.9
         9 x Linux        29.2              18.7
         5 x Linux        10.0               7.2

"% Shared" is the fraction of pages which are shared; "% Reclaimed"
measures how much memory sharing the pages is able to save.

Three systems is still a limited test set.

--Michael Vrable


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  reply	other threads:[~2004-10-26 22:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08  8:59 Shadow page tables? Chengyuan Li
2004-10-08  9:11 ` Keir Fraser
2004-10-10  2:52   ` Chengyuan Li
2004-10-12 18:50   ` Michael Vrable
2004-10-12 20:09     ` Andrew Warfield
2004-10-13  1:53       ` Michael Vrable
2004-10-21  8:38     ` Peri Hankey
2004-10-25 12:12     ` Copy-on-write memory to allow many more xenU domains per machine Peri Hankey
2004-10-25 12:21       ` Ian Pratt
2004-10-25 18:24         ` David Hopwood
2004-10-25 19:52           ` Ronald G. Minnich
2004-10-25 20:19           ` Ian Pratt
2004-10-25 22:38       ` Michael Vrable
2004-10-26  8:15         ` Peri Hankey
2004-10-26 18:30           ` Michael Vrable
2004-10-26 19:43             ` Ian Pratt
2004-10-26 22:19               ` Michael Vrable [this message]
2004-11-02 20:55         ` Jacob Gorm Hansen
2004-11-02 21:33           ` Ian Pratt
2004-11-02 21:50             ` urmk

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=20041026151955.B25506@cs.ucsd.edu \
    --to=mvrable@cs.ucsd.edu \
    --cc=Xen-devel@lists.sourceforge.net \
    /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.