No Wease,
We got the performance improvement after doing the following stuff
--> Reduced the merge factor from 10 to 3.
--> Auto-warming queries as I mentioned in my initial thread.
Thanks,
Johnny
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-performance-very-s
Johnny:
Are you still looking for help?
Wease
-
NOT always nice. When are we getting better releases?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-performance-very-slow-even-after-autowarming-tp2010384p2542789.html
Sent from the Solr - User mailing list archi
Hi Chris,
Thanks for looking into it.
Here is the sample query.
http://localhost:8080/solr/core0/select/?qt=autosuggest&q=a
I am using a request handler with a name autosuggest with the following
configuration.
json
name,score
scor
: 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.
based on the info you've given, there's dozens of posisble reasons why you
might see slow queries -- it's hard to
Alexey,
1) I am using EdgeNGramFilter only in index analyzer alone.
2) Sometimes even multiple characters also creating problems,
What i told was an example for a performance problem, And moreover I am
trying out the autowarming and sometime it is not working ideally [100%
guaranteed performan
* 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
t
