On Wed, Feb 13, 2019 at 11:16 AM Manoj Pillai wrote:
>
>
> On Wed, Feb 13, 2019 at 10:51 AM Raghavendra Gowdappa
> wrote:
>
>>
>>
>> On Tue, Feb 12, 2019 at 5:38 PM Raghavendra Gowdappa
>> wrote:
>>
>>> All,
>>>
>>> We've found perf xlators io-cache and read-ahead not adding any
>>> performance
On Wed, Feb 13, 2019 at 10:51 AM Raghavendra Gowdappa
wrote:
>
>
> On Tue, Feb 12, 2019 at 5:38 PM Raghavendra Gowdappa
> wrote:
>
>> All,
>>
>> We've found perf xlators io-cache and read-ahead not adding any
>> performance improvement. At best read-ahead is redundant due to kernel
>> read-ahead
On Tue, Feb 12, 2019 at 5:38 PM Raghavendra Gowdappa
wrote:
> All,
>
> We've found perf xlators io-cache and read-ahead not adding any
> performance improvement. At best read-ahead is redundant due to kernel
> read-ahead
>
One thing we are still figuring out is whether kernel read-ahead is
tunab
https://review.gluster.org/22203
On Tue, Feb 12, 2019 at 5:38 PM Raghavendra Gowdappa
wrote:
> All,
>
> We've found perf xlators io-cache and read-ahead not adding any
> performance improvement. At best read-ahead is redundant due to kernel
> read-ahead and at worst io-cache is degrading the per
All,
We've found perf xlators io-cache and read-ahead not adding any performance
improvement. At best read-ahead is redundant due to kernel read-ahead and
at worst io-cache is degrading the performance for workloads that doesn't
involve re-read. Given that VFS already have both these functionaliti