* Do you use EdgeNGramFilter in index analyzer only? Or you also use
it on query side as well?

* What if you create additional field first_letter (string) and put
first character/characters (multivalued?) there in your external
processing code. And then during search you can filter all documents
that start with letter "a" using fq=a filter query. Would that solve
your performance problems?

* It makes sense to specify what are you trying to achieve and
probably more people can help you with that.

On Fri, Dec 3, 2010 at 10:47 AM, johnnyisrael <johnnyi.john...@gmail.com> wrote:
>
> Hi,
>
> I am using edgeNgramFilterfactory on SOLR 1.4.1 [<filter
> class="solr.EdgeNGramFilterFactory" maxGramSize="100" minGramSize="1" />]
> for my indexing.
>
> Each document will have about 5 fields in it and only one field is indexed
> with EdgeNGramFilterFactory.
>
> I have about 1.4 million documents in my index now and my index size is
> approx 296MB.
>
> I made the field that is indexed with EdgeNGramFilterFactory as default
> search field. All my query responses are very slow, some of them taking more
> than 10seconds to respond.
>
> All my query responses are very slow, Queries with single letters are still
> very slow.
>
> /select/?q=m
>
> So I tried query warming as follows.
>
> <listener event="newSearcher" class="solr.QuerySenderListener">
>      <arr name="queries">
>        <lst><str name="q">a</str></lst>
>        <lst><str name="q">b</str></lst>
>        <lst><str name="q">c</str></lst>
>        <lst><str name="q">d</str></lst>
>        <lst><str name="q">e</str></lst>
>        <lst><str name="q">f</str></lst>
>        <lst><str name="q">g</str></lst>
>        <lst><str name="q">h</str></lst>
>        <lst><str name="q">i</str></lst>
>        <lst><str name="q">j</str></lst>
>        <lst><str name="q">k</str></lst>
>        <lst><str name="q">l</str></lst>
>        <lst><str name="q">m</str></lst>
>        <lst><str name="q">n</str></lst>
>        <lst><str name="q">o</str></lst>
>        <lst><str name="q">p</str></lst>
>        <lst><str name="q">q</str></lst>
>        <lst><str name="q">r</str></lst>
>        <lst><str name="q">s</str></lst>
>        <lst><str name="q">t</str></lst>
>        <lst><str name="q">u</str></lst>
>        <lst><str name="q">v</str></lst>
>        <lst><str name="q">w</str></lst>
>        <lst><str name="q">x</str></lst>
>        <lst><str name="q">y</str></lst>
>        <lst><str name="q">z</str></lst>
>      </arr>
> </listener>
>
> The same above is done for firstSearcher as well.
>
> My cache settings are as follows.
>
> <filterCache
>      class="solr.LRUCache"
>      size="16384"
>      initialSize="4096"
> autowarmCount="4096"/>
>
> <queryResultCache
>      class="solr.LRUCache"
>      size="16384"
>      initialSize="4096"
> autowarmCount="1024"/>
>
> <documentCache
>      class="solr.LRUCache"
>      size="16384"
>      initialSize="16384"
> />
>
> Still after query warming, few single character search is taking up to 3
> seconds to respond.
>
> Am i doing anything wrong in my cache setting or autowarm setting or am i
> missing anything here?
>
> Thanks,
>
> Johnny
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/Query-performance-very-slow-even-after-autowarming-tp2010384p2010384.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

Reply via email to