From: Mark Nelson <mark.nelson@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "pve-devel@pve.proxmox.com" <pve-devel@pve.proxmox.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Limited IOP/s on Dual Xeon KVM Host
Date: Sat, 10 Nov 2012 07:41:13 -0600 [thread overview]
Message-ID: <509E5979.3070508@inktank.com> (raw)
In-Reply-To: <509E0A65.1040903@profihost.ag>
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?
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.
If you mean that a single Xeon VM instance on a dual Xeon node is faster
than a dual Xeon VM instance, I'm not really sure what to tell you since
you've already tried pinning the processes.
>
> Greets
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-10 13:41 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 [this message]
[not found] ` <509E5979.3070508-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2012-11-10 13:49 ` Stefan Priebe
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=509E5979.3070508@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=pve-devel@pve.proxmox.com \
--cc=s.priebe@profihost.ag \
/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.