From: Dario Faggioli <dario.faggioli@citrix.com>
To: Michael Schinzel <schinzel@ip-projects.de>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: Roger Pau Monne <roger.paumonne@citrix.com>
Subject: Re: Read Performance issue when Xen Hypervisor is activated
Date: Fri, 30 Dec 2016 17:34:58 +0100 [thread overview]
Message-ID: <1483115698.32021.102.camel@citrix.com> (raw)
In-Reply-To: <64f352a7a8a14ec19da5d07374b48eb6@ip-projects.de>
[-- Attachment #1.1: Type: text/plain, Size: 2097 bytes --]
[Cc-ing someone which have done disk benchmark in somewhat recent time]
On Tue, 2016-12-27 at 14:26 +0000, Michael Schinzel wrote:
> We have searched in the last days more and more for the cause of this
> performance issue.
>
> In cooperation with the datacenter, we change some hardware to check,
> if the problem already proceeds. We put the RAID Controller included
> all RAID Arrays to another Supermicro Mainboard: X10SLM-F with only
> one CPU. The result was, we got 400 MB/s read Speed. So it seems
> there is an issue with the Servers Mainboard / CPU and the Xen
> Hypervisor but, we also change the Mainboard to an Supermicro X9DR3-F
> with the actual BIOS Version 3.2a – these also do not solved the
> problem with the performance.
>
> What we also have done:
> - Upgraded Hypervisor from default Debian 8 – 4.4.1 to 4.8.
> - Tested some kernel boot configurations\
>
I think it would be useful to know more about your configuration, e.g.,
are these tests being done in Dom0? How many vCPUs and memory does Dom0
have?
> With an non hypervisor Kernel, the system also uses the read Cache of
> the controller and after some read operations at the same file, it
> gets 1.2 G/s back from the Cache. At Xen Hypervisor Kernel, it seems
> the system do not use any caching operations. I also tested a bit
> with hdparm:
>
> root@v7:~# hdparm -Tt /dev/sdb
>
> /dev/sdb:
> Timing cached reads: 14060 MB in 1.99 seconds = 7076.16 MB/sec
> Timing buffered disk reads: 304 MB in 3.01 seconds = 100.85 MB/sec
>
> This Performance is horrable. It is a RAID 10 with read/write cache
> and SSD Caching functions.
>
> Does somebody know how Xen proceeds with such Caching Systems?
>
>
> Yours sincerely
>
> Michael Schinzel
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-30 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 14:26 Read Performance issue when Xen Hypervisor is activated Michael Schinzel
2016-12-30 16:34 ` Dario Faggioli [this message]
2016-12-30 16:53 ` Michael Schinzel
2016-12-31 9:07 ` Michael Schinzel
2017-01-02 7:15 ` Michael Schinzel
2017-01-12 17:03 ` Dario Faggioli
2017-01-13 13:32 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2016-12-26 11:48 Michael Schinzel
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=1483115698.32021.102.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=roger.paumonne@citrix.com \
--cc=schinzel@ip-projects.de \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).