Erasure coding best practice

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

 



Hi,

Couple of time I saw some use-case in the mail list where people using erasure code on a "weird"  way.
Normally we use more data chunks than coding chunks, like k=4 m=2 or k=8 m=3.
What I mean "weird" I saw someone using k=3 and m=8 (I might remember wrong).

I'm trying to understand what is the benefit of the higher coding chunks? You can use smaller object size?
Let's say 4:2 the minimum object size should be 24K at least or with 8:3  it would be 44K because nothing will be stored on smaller space.
In case of k=3 m=8, smallest object can be 12K, but you can lose 8 nodes (pgs) and data still there?

Ty
_______________________________________________
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