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.
Regards,
Poornima
From: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx>
To: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
Cc: "Poornima Gurusiddaiah" <pgurusid@xxxxxxxxxx>, "Gluster Devel" <gluster-devel@xxxxxxxxxxx>
Sent: Monday, July 17, 2017 11:34:52 AM
Subject: Re: Regarding positioning of nl-cache in gluster client stackOn Mon, Jul 17, 2017 at 11:31 AM, Krutika Dhananjay <kdhananj@xxxxxxxxxx> wrote:So with this background, do you see any issues with loading nl-cache above DHT in the client stack?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.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?Nothing I can think of at the moment.-Krutika
--Pranith
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
