All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastian de Groot <degroot@univention.de>
To: xen-devel@lists.xensource.com
Subject: large overhead with blktap2/vhd
Date: Wed, 23 Jun 2010 17:26:05 +0200	[thread overview]
Message-ID: <201006231726.06620.degroot@univention.de> (raw)

Hi everybody,

I am searching for a copy-on-write solution for Xen and tested blktap2 with 
the vhd backend.

My Test: 

I've created a master-image with "dd" and installed WindowsXP on the image. 
Then I used vhd-util to create a copy-on-write-image for the master-image. 

After booting the VM and logging in the, the cow-image had a size of 260 MB. 
That's a little bit weird, because I didn't really changend any data.

Afterwards I downloaded eclipse in the VM, to see how big the overhead is. The 
eclipse zip-file is 190.64 MB big. But the cow-image had a size of 1468.29 MB 
after downloading eclipse. That's an overhead of 670 %.

Then I unpacked eclipse. So that the actual change in the VM had 425.37 MB. At 
that moment the cow-image was 1979.79 MB big. The result is 365 % Overhead, 
that's better then the result before, but still not very good.

My questions are:
Have I done anything wrong at measuring the overhead?
Is there a bug in blktap2/vhd?
Or is this a usual result?

Here the configuration:
The host is a Xen 4.0 (I compiled it myself) on an 2.6.32-xen-amd64 debian 
kernel  (also self compiled to include some mudules statically). The guest is 
a WindowsXP 32 bit SP2.

I would appreciate your help on that very much.
Bastian

             reply	other threads:[~2010-06-23 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 15:26 Bastian de Groot [this message]
2010-06-24  8:41 ` large overhead with blktap2/vhd Christian Samsel
2010-06-24 11:15   ` Bastian de Groot

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=201006231726.06620.degroot@univention.de \
    --to=degroot@univention.de \
    --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.