<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 19, 2013 at 11:56 AM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 19 June 2013 16:44, cotton-ben <<a href="mailto:ben.cotton@alumni.rutgers.edu" target="_blank">ben.cotton@alumni.rutgers.edu</a>> wrote:<br>
><br>
> />> At the opposite site, I don't see how - as a user - I could optimally<br>
>>> tune a separate container.<br>
><br>
>> I agree that is more difficult to configure, this was one of my points as<br>
>> both a drawback and benefit. It > sounds like in general you don't<br>
>> believe the benefits outweigh the drawbacks then./<br>
><br>
> Hi William. The benefits of your ambition to provide L1 capability<br>
> enhancements -- for /certain/ user's completeness requirements-- definitely<br>
> outweigh the drawbacks . This is a FACT.<br>
<br>
</div>I have to disagree ;-) It certainly is a fact that he's very well<br>
intentioned to make enhancements, but I don't this strategy is proven<br>
the be superior; I'm actually convinced of the opposite.<br>
<br>
We simply cannot assume that the "real data" and the L1 stored entries<br>
will have the same level of hotness, it's actually very likely (since<br>
you like stats) that the entries stored in L1 are frequently accessed,<br>
to the opposite of other entries which - for as far as we know - could<br>
be large and dormant for years.<br></blockquote><div>Actually this is only half true, we know that the values are hot on this node specifically. Other nodes could be requesting the "cold" data quite frequently as well. This could lead to L1 values pushing out distributed data leaving it where nodes have L1 cached values for which the owner doesn't even own. And when the L1 cache value expires there will be no more backup (not including passivation). This is a very odd situation though, since you can't do conditional operations then as well.</div>
<div><br></div><div style>And even with separate containers this is possible to have the L1 discrepency, but actually having a lower lifespan would help remedy this since every once in a while the "hot" value would have to retrieved again from the owning node.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Storing useless data in memory is going to force to evict entries from<br>
L1 which are hot by definition (as they wouldn't be in L1 otherwise -<br>
as you pointed out there likely is an expiry) is a strategy which<br>
actively strives towards a less efficient storage.<br>
<br>
Also L1 timeout can be disabled, making for a very nice self-tuning<br>
adaptive system.<br></blockquote><div>The value cannot be disabled for the timeout. Unless by disable you mean to increase the timeout so high that it will never be hit? Is that a common use case? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span><font color="#888888"><br>
Sanne<br>
</font></span><div><div><br>
><br>
> However, for the /typical/ user's completeness requirements, this FACT<br>
> probably won't be relevant.<br>
><br>
><br>
><br>
> --<br>
> View this message in context: <a href="http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-L1-Data-Container-tp4027447p4027463.html" target="_blank">http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-L1-Data-Container-tp4027447p4027463.html</a><br>
> Sent from the Infinispan Developer List mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div></div>