Hi, It depends of hardware, failure domain, use case, overhead.
I don’t see an easy way to chose k and m values. - Etienne Menguy etienne.men...@croit.io > On 4 Oct 2021, at 16:57, Golasowski Martin <martin.golasow...@vsb.cz> wrote: > > Hello guys, > how does one estimate number of chunks for erasure coded pool ( k = ? ) ? I > see that number of m chunks determines the pool’s resiliency, however I did > not find clear guideline how to determine k. > > Red Hat states that they support only the following combinations: > > k=8, m=3 > k=8, m=4 > k=4, m=2 > > without any rationale behind them. > The table is taken from > https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/storage_strategies_guide/erasure_code_pools. > > Thanks! > > Regards, > Martin > > > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
