> `cpupower idle-set -D 0` will help you a lot, yes.
>
> However it seems that not only the bluestore makes it slow. >= 50% of the
> latency is introduced by the OSD itself. I'm just trying to understand
> WHAT parts of it are doing so much work. For example in my current case
> (with cpupower
On 3/20/19 3:12 AM, Vitaliy Filippov wrote:
`cpupower idle-set -D 0` will help you a lot, yes.
However it seems that not only the bluestore makes it slow. >= 50% of
the latency is introduced by the OSD itself. I'm just trying to
understand WHAT parts of it are doing so much work. For example
`cpupower idle-set -D 0` will help you a lot, yes.
However it seems that not only the bluestore makes it slow. >= 50% of the
latency is introduced by the OSD itself. I'm just trying to understand
WHAT parts of it are doing so much work. For example in my current case
(with cpupower
On 19/03/2019 16:17, jes...@krogh.cc wrote:
Hi All.
I'm trying to get head and tails into where we can stretch our Ceph cluster
into what applications. Parallism works excellent, but baseline throughput
it - perhaps - not what I would expect it to be.
Luminous cluster running bluestore -
> One thing you can check is the CPU performance (cpu governor in
> particular).
> On such light loads I've seen CPUs sitting in low performance mode (slower
> clocks), giving MUCH worse performance results than when tried with
> heavier
> loads. Try "cpupower monitor" on OSD nodes in a loop and
One thing you can check is the CPU performance (cpu governor in particular).
On such light loads I've seen CPUs sitting in low performance mode (slower
clocks), giving MUCH worse performance results than when tried with heavier
loads. Try "cpupower monitor" on OSD nodes in a loop and observe
Hi All.
I'm trying to get head and tails into where we can stretch our Ceph cluster
into what applications. Parallism works excellent, but baseline throughput
it - perhaps - not what I would expect it to be.
Luminous cluster running bluestore - all OSD-daemons have 16GB of cache.
Fio files
