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

[Krutika Dhananjay]

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?

-Krutika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170717/5445d8b7/attachment.html>