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
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
