it didnt make a difference. I will try to re-configure with a 2x3 config
On Fri, Aug 31, 2018 at 1:48 PM Raghavendra Gowdappa
wrote:
> another relevant option is setting cluster.lookup-optimize on.
>
> On Fri, Aug 31, 2018 at 3:22 PM, Davide Obbi
> wrote:
>
>> #gluster vol set VOLNAME group
another relevant option is setting cluster.lookup-optimize on.
On Fri, Aug 31, 2018 at 3:22 PM, Davide Obbi
wrote:
> #gluster vol set VOLNAME group nl-cache --> didn't know there are groups
> of options, after this command i got set the following:
> performance.nl-cache-timeout: 600
>
#gluster vol set VOLNAME group nl-cache --> didn't know there are groups of
options, after this command i got set the following:
performance.nl-cache-timeout: 600
performance.nl-cache: on
performance.parallel-readdir: on
performance.io-thread-count: 64
network.inode-lru-limit: 20
to note that
To enable nl-cache please use group option instead of single volume set:
#gluster vol set VOLNAME group nl-cache
This sets few other things including time out, invalidation etc.
For enabling the option Raghavendra mentioned, you ll have to execute it
explicitly, as it's not part of group option
On Thu, Aug 30, 2018 at 8:38 PM, Davide Obbi
wrote:
> yes "performance.parallel-readdir on and 1x3 replica
>
That's surprising. I thought performance.parallel-readdir will help only
when distribute count is fairly high. This is something worth investigating
further.
> On Thu, Aug 30, 2018 at
yes "performance.parallel-readdir on and 1x3 replica
On Thu, Aug 30, 2018 at 5:00 PM Raghavendra Gowdappa
wrote:
>
>
> On Thu, Aug 30, 2018 at 8:08 PM, Davide Obbi
> wrote:
>
>> Thanks Amar,
>>
>> i have enabled the negative lookups cache on the volume:
>>
>> To deflate a tar archive (not
On Thu, Aug 30, 2018 at 8:08 PM, Davide Obbi
wrote:
> Thanks Amar,
>
> i have enabled the negative lookups cache on the volume:
>
> To deflate a tar archive (not compressed) of 1.3GB it takes aprox 9mins
> which can be considered a slight improvement from the previous 12-15
> however still not
