lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yao <...@ford.com>
Subject Re: Date faceting and memory leaks
Date Tue, 18 May 2010 00:53:23 GMT

Chris,

Thanks for the detailed response. No I am not using Date Facet but Facet
Query as for facet display. Here is the full configuration of my "dismax"
query handler:

  <requestHandler name="dismax" class="solr.SearchHandler" >
    <lst name="defaults">
     <str name="defType">dismax</str>
     <str name="echoParams">explicit</str>
     <float name="tie">0.01</float>
     <str name="qf">
        title text^0.5 domain^0.1 nature^0.1 author
     </str>
     <str name="pf">
        title text
     </str>
     <str name="bf">
        recip(ms(NOW,last_modified),3.16e-11,1,1)
     </str>
     <str name="fl">
        url,title,domain,nature,src,last_modified,text,sz
     </str>
     <str name="mm">
        2&lt;-1 5&lt;-2 6&lt;90%
     </str>
     <int name="ps">100</int>
     <str name="q.alt">*:*</str>
     <!-- example highlighter config, enable per-query with hl=true -->
     <str name="hl">on</str>
     <str name="hl.fl">title,text</str>
     <!-- for this field, we want no fragmenting, just highlighting -->
     <str name="f.title.hl.fragsize">0</str>
     <str name="f.text.hl.snippets">3</str>
     <!-- instructs Solr to return the field itself if no query terms are
          found -->
     <str name="f.text.hl.alternateField">text</str>
     <str name="f.text.h1.maxAlternateFieldLength">400</str>
     <str name="f.text.hl.fragmenter">regex</str> <!-- defined below -->
    </lst>
    <lst name="appends">
     <str name="facet.field">{!ex=src}src</str>
     <str name="facet.field">{!ex=domain}domain</str>
     <str name="facet.field">{!ex=nature}nature</str>
     <str name="facet.query">{!ex=last_modified}last_modified:[NOW-30DAY TO
*]</str>
     <str name="facet.query">{!ex=last_modified}last_modified:[NOW-90DAY TO
NOW-30DAY]</str>
     <str name="facet.query">{!ex=last_modified}last_modified:[NOW-180DAY TO
NOW-90DAY]</str>
     <str name="facet.query">{!ex=last_modified}last_modified:[NOW-365DAY TO
NOW-180DAY]</str>
     <str name="facet.query">{!ex=last_modified}last_modified:[NOW-730DAY TO
NOW-365DAY]</str>
     <str name="facet.query">{!ex=last_modified}last_modified:[* TO
NOW-730DAY]</str>
    </lst>
  </requestHandler>

Cache settings:
  <filterCache class="solr.LRUCache" size="1512000" initialSize="1512000"
autowarmCount="1280"/>
  <queryResultCache  class="solr.LRUCache" size="512"  initialSize="512"  
autowarmCount="32"/>
  <documentCache class="solr.LRUCache"  size="512"  initialSize="512" 
autowarmCount="0"/>

I am monitoring Solr JVM Heap Memory Usage via remote Jconsole, the image
below shows how heap size keep increasing as more facet query requests being
sent the Solr via JMeter:
http://n3.nabble.com/file/n825038/memory-1.jpg 

The following is the request URL pattern:
select?rows=0&facet=true&facet.mincount=1&facet.method=enum&q=${query}&qt=dismax
where ${query} is selected randomly from a list of 100 query terms

The date rounding suggest is a very good one, I will need to rerun the test
and report back on the cache setting. I remember my filterCache hit ratio is
around 0.7. I did use the tagged results for multi-select display of facet
values but in this case there is no fq in the load test request URL.

Thanks again and I will report back on the re-run with date rounding.

-- 
View this message in context: http://lucene.472066.n3.nabble.com/Date-faceting-and-memory-leaks-tp824372p825038.html
Sent from the Solr - User mailing list archive at Nabble.com.

Mime
View raw message