From: Stefan Priebe <s.priebe@profihost.ag>
To: "pve-devel@pve.proxmox.com" <pve-devel@pve.proxmox.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Limited IOP/s on Dual Xeon KVM Host
Date: Sat, 10 Nov 2012 09:03:49 +0100 [thread overview]
Message-ID: <509E0A65.1040903@profihost.ag> (raw)
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?
Greets
Stefan
next reply other threads:[~2012-11-10 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 8:03 Stefan Priebe [this message]
2012-11-10 13:41 ` Limited IOP/s on Dual Xeon KVM Host Mark Nelson
[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=509E0A65.1040903@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=pve-devel@pve.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox