<div dir="ltr">Martin,<div><br></div><div style>While those are implementation details, I think some adjustment should be allowed for tuning purposes. There should be some reasonable values. On the other hand, I think that, for the expiration db directory, and data directory - perhaps we should default somehow. Eg.,</div>
<div style><br></div><div style><span style="color:rgb(0,0,0);font-family:Consolas,'Liberation Mono',Courier,monospace;font-size:12px;line-height:16px;white-space:pre"><leveldb-store path="leveldb-nc"...</span>>...</...></div>
<div style><br></div><div style>A data directory can be created in leveldb-nc/data, and expiration directory can be created in leveldb-nc/expired</div><div style><br></div><div style>What do you guys feel?</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Sep 11, 2013 at 5:46 AM, Martin Gencur <span dir="ltr"><<a href="mailto:mgencur@redhat.com" target="_blank">mgencur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Adding Ray.<br>
<br>
Ray, can you please comment on this?<br>
<br>
Thanks<br>
<span class="HOEnZb"><font color="#888888">Martin<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 11.9.2013 11:34, Martin Gencur wrote:<br>
> Hi,<br>
> let's look at configuration of LevelDB in Infinispan Server:<br>
> <a href="https://gist.github.com/mgencur/6520948" target="_blank">https://gist.github.com/mgencur/6520948</a><br>
><br>
> After investigating what the <expiration> configuration element is good<br>
> for, I think it's an implementation detail and should be removed.<br>
><br>
> Every time a mortal entry is stored in the cache, it's put (in internal<br>
> format of the cache store - ExpiryEntry) in an expiryEntryQueue whose<br>
> size is specified in the configuration through "queue-size" attribute.<br>
> The path attribute (location of dbExpired) is only used when purge() is<br>
> called on the cache store. At that moment, all entries that are in the<br>
> expiryEntryQueue are flushed into dbExpired (location specified through<br>
> "path"), all the elements from dbExpired are read and if they have<br>
> expiry time shorter than current time, they are removed from the primary<br>
> cache store's location, i.e. they are purged.<br>
><br>
> IMO, the location where intermediate (ExpiryEntry) are stored is an<br>
> implementation (users don't have access to it anyway) detail and the<br>
> queue-size attribute is a black-box users will never know how to set it.<br>
> I would suggest hiding these implementation details and simplify the<br>
> configuration. There are way too many configuration elements already.<br>
><br>
> WDYT?<br>
><br>
> Thanks<br>
> Martin<br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">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>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">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>