From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: ceph-devel@vger.kernel.org, Sage Weil <sage@inktank.com>
Subject: Re: ceph-osd cpu usage
Date: Fri, 16 Nov 2012 10:11:36 +0100 [thread overview]
Message-ID: <50A60348.5080604@profihost.ag> (raw)
In-Reply-To: <f23bc508-a0c1-445d-a2bd-062898847507@mailpro>
Am 16.11.2012 09:41, schrieb Alexandre DERUMIER:
>>> Any other ideas how to reduce ceph-osd while doing randwrite?
>>>
>>> Randread gives me with 3 VMs: 60.000 iops
>>> Randwrite gives me with 3 VMs: 25.000 iops
>
> Great to see that read scale !
Yes that works fine.
> For randwrite, what is the bottleneck now with filestore xattr use omap = true ?
Oh no the result was still with default fsetxattr. Filestore xattr use
omap added another 20% load an resultet in much lower iops. Seems i
wasn't clear enough about that.
Stefan
prev parent reply other threads:[~2012-11-16 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 10:56 ceph-osd cpu usage Stefan Priebe - Profihost AG
2012-11-15 11:18 ` Alexandre DERUMIER
2012-11-15 12:19 ` Stefan Priebe - Profihost AG
2012-11-15 15:12 ` Mark Nelson
2012-11-15 16:09 ` Stefan Priebe
2012-11-15 16:52 ` Sage Weil
2012-11-15 19:44 ` Stefan Priebe
2012-11-15 15:14 ` Sage Weil
2012-11-15 15:30 ` Stefan Priebe - Profihost AG
2012-11-15 20:26 ` Stefan Priebe
2012-11-16 8:41 ` Alexandre DERUMIER
2012-11-16 9:11 ` Stefan Priebe - Profihost AG [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=50A60348.5080604@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@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 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.