<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 17, 2017 at 11:31 AM, Krutika Dhananjay <span dir="ltr"><<a href="mailto:kdhananj@redhat.com" target="_blank">kdhananj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Poornima and Pranith,<br><br></div>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?<br><br></div>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.<br><br></div>So with this background, do you see any issues with loading nl-cache above DHT in the client stack?<span class="HOEnZb"><font color="#888888"><br></font></span></div></div></blockquote><div><br></div><div>Nothing I can think of at the moment.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">-Krutika<br></font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>