From: Stefan Priebe <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: Mark Nelson <mark.nelson-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
Cc: "ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"pve-devel-KmHT29P9Uc/4CZzEM2C48g@public.gmane.org"
<pve-devel-KmHT29P9Uc/4CZzEM2C48g@public.gmane.org>
Subject: Re: Limited IOP/s on Dual Xeon KVM Host
Date: Sat, 10 Nov 2012 14:49:11 +0100 [thread overview]
Message-ID: <509E5B57.1050004@profihost.ag> (raw)
In-Reply-To: <509E5979.3070508-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
Am 10.11.2012 14:41, schrieb Mark Nelson:
> On 11/10/2012 02:03 AM, Stefan Priebe wrote:
>> Hello lists,
>>
>> on a dual Xeon KVM Host i get max 6000 IOP/s random 4k writes AND reads.
>> On a Single Xeon KVM Host i get 17.000-18.000 IOP/s write and read. I
>> already tried to pin the kvm process using numactl and also the fio
>> process but it doesn't help on the dual xeon.
>>
>> 10GBE Network is fine. I get 9.8Gbit/s on both hosts. Kernel is also he
>> same on both.
>>
>> Anybody an idea?
>
> When you say KVM host, do you mean the underlying node or the virtual
> machine instance?
Sorry i'm talking about the vm host regarding the HW. The vm instance is
always the same.
> If you mean underlying node, it could be remote memory access or if you
> are on a last gen xeon if you have dual io hubs, you could be hitting a
> remote io hub for the network card. I wouldn't think that would cause
> such a big hit, but those are things to look into.
I'm on E5-Xeon. What means io hub?
Stefan
next prev parent reply other threads:[~2012-11-10 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 8:03 Limited IOP/s on Dual Xeon KVM Host Stefan Priebe
2012-11-10 13:41 ` Mark Nelson
[not found] ` <509E5979.3070508-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2012-11-10 13:49 ` Stefan Priebe [this message]
2012-11-10 16:00 ` Andrey Korolyov
2012-11-10 19:16 ` Stefan Priebe
2012-11-10 21:21 ` Stefan Priebe
2012-11-11 9:14 ` Dietmar Maurer
2012-11-11 12:04 ` Stefan Priebe
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=509E5B57.1050004@profihost.ag \
--to=s.priebe-2lf/h1ldwehr5kwtpvns9a@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.nelson-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org \
--cc=pve-devel-KmHT29P9Uc/4CZzEM2C48g@public.gmane.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