From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Joao Eduardo Luis <joao.luis@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: less cores more iops / speed
Date: Thu, 08 Nov 2012 09:45:17 +0100 [thread overview]
Message-ID: <509B711D.3070206@profihost.ag> (raw)
In-Reply-To: <509B03EA.9050701@inktank.com>
Am 08.11.2012 01:59, schrieb Mark Nelson:
> There's also the context switching overhead. It'd be interesting to
> know how much the writer processes were shifting around on cores.
What do you mean by that? I'm talking about the KVM guest not about the
ceph nodes.
> Stefan, what tool were you using to do writes?
as always: fio ;-)
Stefan
next prev parent reply other threads:[~2012-11-08 8:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 22:02 less cores more iops / speed Stefan Priebe
2012-11-08 0:00 ` Joao Eduardo Luis
2012-11-08 0:16 ` Openstack - Boot From New Volume Quenten Grasso
2012-11-08 0:59 ` less cores more iops / speed Mark Nelson
2012-11-08 8:45 ` Stefan Priebe - Profihost AG [this message]
2012-11-08 8:58 ` Alexandre DERUMIER
2012-11-08 9:02 ` Stefan Priebe - Profihost AG
2012-11-08 9:05 ` Alexandre DERUMIER
2012-11-08 9:28 ` Stefan Priebe - Profihost AG
2012-11-08 13:19 ` Mark Nelson
2012-11-08 15:14 ` Stefan Priebe - Profihost AG
2012-11-08 15:53 ` Alexandre DERUMIER
2012-11-08 21:52 ` Andrey Korolyov
2012-11-09 8:43 ` Stefan Priebe - Profihost AG
2012-11-08 0:59 ` Mark Nelson
2012-11-08 5:42 ` Dietmar Maurer
2012-11-08 5:49 ` Dietmar Maurer
2012-11-08 6:20 ` Stefan Priebe - Profihost AG
2012-11-08 5:49 ` Stefan Priebe - Profihost AG
2012-11-08 5:54 ` Dietmar Maurer
2012-11-08 6:21 ` Stefan Priebe - Profihost AG
-- strict thread matches above, loose matches on Subject: below --
2012-11-12 15:33 [pve-devel] " Stefan Priebe - Profihost AG
[not found] ` <50A116DC.2020509-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2012-11-12 15:39 ` Alexandre DERUMIER
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=509B711D.3070206@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=joao.luis@inktank.com \
--cc=mark.nelson@inktank.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