Question regarding Quincy mclock scheduler.

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

 



Hi,
We have a quincy 17.2.5 based cluster, and we have some question
regarding the mclock iops scheduler.
Looking into the documentation, the default profile is the HIGH_CLIENT_OPS
that mean that 50% of IOPS for an OSD are reserved for clients operations.

But looking into OSD configuration settings, it seems that this is not the case or probably there is something I don't understand.

ceph config get osd.0 osd_mclock_profile
high_client_ops



ceph config show osd.0 | grep mclock
osd_mclock_max_capacity_iops_hdd                 22889.222997       mon
osd_mclock_scheduler_background_best_effort_lim  999999 default
osd_mclock_scheduler_background_best_effort_res 1144 default
osd_mclock_scheduler_background_best_effort_wgt  2                 default
osd_mclock_scheduler_background_recovery_lim 4578 default osd_mclock_scheduler_background_recovery_res 1144 default
osd_mclock_scheduler_background_recovery_wgt     1                 default
osd_mclock_scheduler_client_lim 999999 default osd_mclock_scheduler_client_res 2289 default
osd_mclock_scheduler_client_wgt                  2                 default

So i have osd_mclock_max_capacity_iops_hdd = 22889.222997 why osd_mclock_scheduler_client_res is not 11444 ?

this value seem strange to me.

Kr
Philippe
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux