[Gluster-devel] Regarding positioning of nl-cache in gluster client stack

[Pranith Kumar Karampuri]

On Mon, Jul 17, 2017 at 11:42 AM, Poornima Gurusiddaiah <pgurusid at redhat.com
> wrote:

>
> The only requirement on positioning of nl-cache is its good to load it
> below md-cache.
> It should be ok to load it between shard and DHT.
>

One good thing I can think of doing this is that the stress case of too
many files in a directory and how nl-cache will behave will be tested
regularly.


>
> Regards,
> Poornima
> ------------------------------
>
> *From: *"Pranith Kumar Karampuri" <pkarampu at redhat.com>
> *To: *"Krutika Dhananjay" <kdhananj at redhat.com>
> *Cc: *"Poornima Gurusiddaiah" <pgurusid at redhat.com>, "Gluster Devel" <
> gluster-devel at gluster.org>
> *Sent: *Monday, July 17, 2017 11:34:52 AM
> *Subject: *Re: Regarding positioning of nl-cache in gluster client stack
>
>
>
>
> On Mon, Jul 17, 2017 at 11:31 AM, Krutika Dhananjay <kdhananj at redhat.com>
> wrote:
>
>> Hi Poornima and Pranith,
>>
>> I see that currently glusterd loads nl-cache between stat-prefetch and
>> open-behind on the client stack. Were there any specific considerations for
>> selecting this position for nl-cache?
>>
>> I was interested to see the performance impact of loading this translator
>> between shard and DHT in the VM store use case stack in terms of reducing
>> the number of lookups shard would have to do to figure out if a shard is
>> already created or not, since shard does its own management of .shard and
>> the files under it.
>>
>> So with this background, do you see any issues with loading nl-cache
>> above DHT in the client stack?
>>
>
> Nothing I can think of at the moment.
>
>
>>
>> -Krutika
>>
>
>
>
> --
> Pranith
>
>
>


-- 
Pranith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170717/fce78d97/attachment-0001.html>