<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 11.9.2013 19:01, Ray Tsang wrote:<br>
    </div>
    <blockquote
cite="mid:CAD4EjTJZQ0eLP7Q8Au9hsCD75d_qfpf1q2JH6u_CO0iMxhBj4A@mail.gmail.com"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">Martin,
        <div><br>
        </div>
        <div>While those are implementation details, I think some
          adjustment should be allowed for tuning purposes. &nbsp;There
          should be some reasonable values. &nbsp;On the other hand, I think
          that, for the expiration db directory, and data directory -
          perhaps we should default somehow. &nbsp;Eg.,</div>
        <div><br>
        </div>
        <div><span>&lt;leveldb-store path="leveldb-nc"...</span>&gt;...&lt;/...&gt;</div>
        <div><br>
        </div>
        <div>A data directory can be created in leveldb-nc/data, and
          expiration directory can be created in leveldb-nc/expired</div>
        <div><br>
        </div>
        <div>What do you guys feel?</div>
      </div>
    </blockquote>
    <br>
    I think this is a good idea. <br>
    <br>
    Martin<br>
    <br>
    <blockquote
cite="mid:CAD4EjTJZQ0eLP7Q8Au9hsCD75d_qfpf1q2JH6u_CO0iMxhBj4A@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <br>
        <br>
        <div class="gmail_quote">On Wed, Sep 11, 2013 at 5:46 AM, Martin
          Gencur <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:mgencur@redhat.com" target="_blank">mgencur@redhat.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote">
            Adding Ray.<br>
            <br>
            Ray, can you please comment on this?<br>
            <br>
            Thanks<br>
            <span class="HOEnZb">Martin<br>
            </span>
            <div class="HOEnZb">
              <div class="h5"><br>
                On 11.9.2013 11:34, Martin Gencur wrote:<br>
                &gt; Hi,<br>
                &gt; let's look at configuration of LevelDB in
                Infinispan Server:<br>
                &gt; <a moz-do-not-send="true"
                  href="https://gist.github.com/mgencur/6520948"
                  target="_blank">https://gist.github.com/mgencur/6520948</a><br>
                &gt;<br>
                &gt; After investigating what the &lt;expiration&gt;
                configuration element is good<br>
                &gt; for, I think it's an implementation detail and
                should be removed.<br>
                &gt;<br>
                &gt; Every time a mortal entry is stored in the cache,
                it's put (in internal<br>
                &gt; format of the cache store - ExpiryEntry) in an
                expiryEntryQueue whose<br>
                &gt; size is specified in the configuration through
                "queue-size" attribute.<br>
                &gt; The path attribute (location of dbExpired) is only
                used when purge() is<br>
                &gt; called on the cache store. At that moment, all
                entries that are in the<br>
                &gt; expiryEntryQueue are flushed into dbExpired
                (location specified through<br>
                &gt; "path"), all the elements from dbExpired are read
                and if they have<br>
                &gt; expiry time shorter than current time, they are
                removed from the primary<br>
                &gt; cache store's location, i.e. they are purged.<br>
                &gt;<br>
                &gt; IMO, the location where intermediate (ExpiryEntry)
                are stored is an<br>
                &gt; implementation (users don't have access to it
                anyway) detail and the<br>
                &gt; queue-size attribute is a black-box users will
                never know how to set it.<br>
                &gt; I would suggest hiding these implementation details
                and simplify the<br>
                &gt; configuration. There are way too many configuration
                elements already.<br>
                &gt;<br>
                &gt; WDYT?<br>
                &gt;<br>
                &gt; Thanks<br>
                &gt; Martin<br>
                &gt; _______________________________________________<br>
                &gt; infinispan-dev mailing list<br>
                &gt; <a moz-do-not-send="true"
                  href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
                &gt; <a moz-do-not-send="true"
                  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 moz-do-not-send="true"
                  href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
                <a moz-do-not-send="true"
                  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>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
infinispan-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></pre>
    </blockquote>
    <br>
  </body>
</html>