From: Mark Nelson <mnelson@redhat.com>
To: Junqin JQ7 Zhang <zhangjq7@lenovo.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Ceph Bluestore OSD CPU utilization
Date: Tue, 11 Jul 2017 06:32:11 -0500 [thread overview]
Message-ID: <6929185c-7c88-83ee-9e12-62db1cd23ec5@redhat.com> (raw)
In-Reply-To: <5f6e1242-f0ec-62f2-9778-eb0a28406838@redhat.com>
Ugh, small sequential *reads* I meant to say. :)
Mark
On 07/11/2017 06:31 AM, Mark Nelson wrote:
> Hi Junqin,
>
> Can you tell us your hardware configuration (models and quantities of
> cpus, network cards, disks, ssds, etc) and the command and options you
> used to measure performance?
>
> In many cases bluestore is faster than filestore, but there are a couple
> of cases where it is notably slower, the big one being when doing small
> sequential writes without client-side readahead.
>
> Mark
>
> On 07/11/2017 05:34 AM, Junqin JQ7 Zhang wrote:
>> Hi,
>>
>> I installed Ceph luminous v12.1.0 in 3 nodes cluster with BlueStore
>> and did some fio test.
>> During test, I found the each OSD CPU utilization rate was only aroud
>> 30%.
>> And the performance seems not good to me.
>> Is there any configuration to help increase OSD CPU utilization to
>> improve performance?
>> Change kernel.pid_max? Any BlueStore specific configuration?
>>
>> Thanks a lot!
>>
>> B.R.
>> Junqin Zhang
>> --
>> 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
>>
> --
> 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:[~2017-07-11 11:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 10:34 Ceph Bluestore OSD CPU utilization Junqin JQ7 Zhang
2017-07-11 11:31 ` Mark Nelson
2017-07-11 11:32 ` Mark Nelson [this message]
2017-07-11 15:31 ` Junqin JQ7 Zhang
2017-07-11 15:46 ` Mark Nelson
2017-07-12 2:44 ` Junqin JQ7 Zhang
2017-07-12 10:21 ` Junqin JQ7 Zhang
2017-07-12 15:29 ` Mark Nelson
2017-07-13 13:37 ` Junqin JQ7 Zhang
2017-07-27 2:40 ` Brad Hubbard
2017-07-27 3:55 ` Mark Nelson
2017-07-28 10:34 ` Junqin JQ7 Zhang
2017-08-02 10:39 ` Junqin JQ7 Zhang
2017-08-02 13:15 ` Mark Nelson
2017-07-28 20:57 ` Jianjian Huo
2017-07-30 3:34 ` Mark Nelson
2017-07-31 18:29 ` Jianjian Huo
2017-07-31 19:23 ` Mark Nelson
2017-08-03 23:28 ` Jianjian Huo
2017-08-01 7:35 ` Mohamad Gebai
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=6929185c-7c88-83ee-9e12-62db1cd23ec5@redhat.com \
--to=mnelson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=zhangjq7@lenovo.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.