From: Stefan Priebe <s.priebe@profihost.ag>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Andrey Korolyov <andrey@xdel.ru>,
Mark Nelson <mark.nelson@inktank.com>,
"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: Sun, 11 Nov 2012 13:04:58 +0100 [thread overview]
Message-ID: <509F946A.7030004@profihost.ag> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75577EFDD0@lisa.maurer-it.com>
Am 11.11.2012 10:14, schrieb Dietmar Maurer:
>> Got it fixed by Bios update... crazy.
>
> So you can't see any regression in IOPS with more cores?
In this subject i wasn't talking about simply more cores in VM but about
having a Dual Xeon instead of a Single Xeon as host.
It seems Supermicro just had a bug in their X9 Dual Socket mainboard bios...
> Can you speedup things with process pinning?
> Just want to make sure that NUMA does not play any role here.
Yes i still can speed up with pinning but this also applies to a Single
Xeon. When i pin the fio process inside VM i get 18.000 instead of
15.000 iops.
Greets,
Stefan
prev parent reply other threads:[~2012-11-11 12:04 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
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 [this message]
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=509F946A.7030004@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=andrey@xdel.ru \
--cc=ceph-devel@vger.kernel.org \
--cc=dietmar@proxmox.com \
--cc=mark.nelson@inktank.com \
--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 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.