All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Bier" <peter_bier@web.de>
To: xen-devel@lists.xensource.com
Subject: Re: Welcome to the "Xen-devel" mailing list
Date: Mon, 28 Mar 2005 13:35:42 +0100	[thread overview]
Message-ID: <1622716546@web.de> (raw)

This is a try to post a follow-up to the thread "poor domU VBD performance" in the new newsgroup.
I do not know if this is th adequate way to do so, but I did not find any information on how to do 
so otherwise.

This is a response to "Ian Pratt":

Yes I do the performance testing using dd. It's only a simple "benchmark" but its results seem to indicate
a fundamental issue. I did the tests with the same partitions from DOM0 just as DomU. I used both disks 
and Dom0 achieved in all experiments 2.5 times the transfer rate of DomU. 

I do not know the chipset of my IDE controller on my computer at home, while I know that in the office it
pas a Promise raid controller ( I am neither at home nor in the office momentarily ) . I am sure, that the
system was idle during all test ( meaning that there was only the standard system running with no busy 
jobs and no user program consuming CPU or IO resources. 

I am very interested about Xen, but I need to fiy that problem. 
If there is any "checklist" how to  configure XEN efficiently, I might be able to fix the problem myself

Thanks 

    Peter Bier 
 

______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

             reply	other threads:[~2005-03-28 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 12:35 Peter Bier [this message]
2005-03-28 11:53 ` Re: Welcome to the "Xen-devel" mailing list James Bulpin
     [not found] <mailman.0.1238123711.30951.xen-devel@lists.xensource.com>
2009-03-27  3:19 ` Steven

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=1622716546@web.de \
    --to=peter_bier@web.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.