Re: throttling reweight-by-utilization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 3, 2016 at 3:15 AM, Sage Weil <sage@xxxxxxxxxxxx> wrote:
> Latest branch:
>
>         https://github.com/liewegas/ceph/commits/wip-reweight
>
> I made several changes:
>
> - new command, 'osd utilization'
>
> avg 51
> stddev 0.707107 (expected baseline 6.68019)

Sage, sorry for bringing this up again. I don't quite understand what
the "expected baseline" is for. per the code,

float edev = sqrt(avg_pg * (1.0 - (1.0 / (double)num_up_in)));

so it sounds sound sort of std dev, but the unit of std dev here is
the "number of pg", while edev's unit is
num_pg^{1/2}, so it's not comparable with avg_pg or the
{base,new}_stddev. so could you shed some light on how we shall use
this number as a reference?
and what's the meaning of this number?

thanks.

> min osd.3 with 52 pgs (1.01961 * mean)
> max osd.3 with 50 pgs (0.980392 * mean)
>
> (json version too)
>
> - new commands: osd test-reweight-by-{pg,utilization}
>
> same as osd reweight-by-*, but it doesn't actually to it--just shows the
> before and after stats:
>
> no change
> moved 2 / 408 (0.490196%)
> avg 51
> stddev 5.26783 -> 4.74342 (expected baseline 6.68019)
> min osd.3 with 59 -> 57 pgs (1.15686 -> 1.11765 * mean)
> max osd.3 with 41 -> 42 pgs (0.803922 -> 0.823529 * mean)
>
> oload 105
> max_change 0.05
> average 51.000000
> overload 53.550000
> osd.3 weight 1.000000 -> 0.950012
> osd.2 weight 1.000000 -> 0.950012
>
>


-- 
Regards
Kefu Chai
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux