lists.ceph.com, Lazuardi Nasution
>
> Subject: Re: [ceph-users] RBD Stripe/Chunk Size (Order Number) Pros
> Cons
> Message-ID: <100239228.47.1466160323...@ox.pcextreme.nl>
> Content-Type: text/plain; charset=UTF-8
>
>
> > Op 17 juni 2016 om 12:12 schre
Works great for them.
Wido
> Anyway, I love coffee too :)
>
> Best regards,
>
>
> > Date: Thu, 16 Jun 2016 04:01:37 -0500
> > From: Mark Nelson
> > To: ceph-users@lists.ceph.com
> > Subject: Re: [ceph-users] RBD Stripe/Chunk Size (Order Number) Pros
> >
Nelson
> To: ceph-users@lists.ceph.com
> Subject: Re: [ceph-users] RBD Stripe/Chunk Size (Order Number) Pros
> Cons
> Message-ID:
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
>
> On 06/16/2016 03:54 AM, Mark Nelson wrote:
> > Hi,
> &g
On 06/16/2016 03:54 AM, Mark Nelson wrote:
Hi,
larger stripe size (to an extent) will generally improve large
sequential read and write performance.
Oops, I should have had my coffee. I missed a sentence here. larger
strip size will generally improve large sequential read and write
perfor
Hi,
larger stripe size (to an extent) will generally improve large
sequential read and write performance. There's overhead though. It
means more objects which can slow things down at the filestore level
when PG splits occur and also potentially means more inodes fall out of
cache, longer sy
