Well, I use Solr 1.4. There are 30698 lines in my elevation file. I need only 20 results response back at a time.
On Sun, Oct 31, 2010 at 9:12 AM, Lance Norskog <goks...@gmail.com> wrote: > Now you got me interested. Always a bad thing ;) > > Looking at the QueryElevationComponent, I don't know enough to decide > if it has algorithms that don't scale. It does something odd with > sorting. It has a concurrent access path for each query, which should > not be a problem. It has not changed much since a year ago. > > Which Solr release are you using? If it is the trunk or 3.x, it's > possible that the Lucene API changes have left QE very slow. > > Also, how many lines are in your elevation file? How many "answers" do > you supply per query? It is possible that the special tricks QE does > with sorting don't scale to large elevation database or large numbers > of results per query. > > Lance > > On Fri, Oct 29, 2010 at 7:04 AM, Chamnap Chhorn <chamnapchh...@gmail.com> > wrote: > > Thanks for reply. > > > > I'm looking for how to improve the speed of the search query. The > > QueryElevation Component is taking too much time which is > > unacceptable. The size of elevation file is only 1 Mb. I wonder other > > people using this component without problems (related to speed)? Am I > > using it the wrong way or there is a limit when using this component? > > > > On 10/29/10, Lance Norskog <goks...@gmail.com> wrote: > >> I do not know if this is accurate. There are direct tools to monitor > >> these problems: jconsole, visualgc/visualvm, YourKit, etc. Often these > >> counts allot many things to one place that should be spread out. > >> > >> On Fri, Oct 29, 2010 at 12:27 AM, Chamnap Chhorn > >> <chamnapchh...@gmail.com> wrote: > >>> anyone has some suggestions to improve the search? > >>> thanks > >>> > >>> On 10/28/10, Chamnap Chhorn <chamnapchh...@gmail.com> wrote: > >>>> Sorry for very bad pasting. I paste it again. > >>>> > >>>> Slowest Components Count > Exclusive > >>>> Total > >>>> QueryElevationComponent 1 506,858 > ms > >>>> 100% > >>>> 506,858 ms 100% > >>>> SolrIndexSearcher 1 2.0 ms > >>>> 0% 2.0 ms 0% > >>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter() 1 1.0 ms > >>>> 0% 506,862 ms 100% > >>>> QueryComponent 1 1.0 > ms > >>>> 0% 1.0 ms 0% > >>>> DebugComponent 1 0.0 > ms > >>>> 0% 0.0 ms 0% > >>>> FacetComponent 1 0.0 > ms > >>>> 0% 0.0 ms 0% > >>>> > >>>> On Thu, Oct 28, 2010 at 4:57 PM, Chamnap Chhorn > >>>> <chamnapchh...@gmail.com>wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I'm using solr 1.4 and using QueryElevation Component for guaranteed > >>>>> search > >>>>> position. I have around 700,000 documents with 1 Mb elevation file. > It > >>>>> turns > >>>>> out it is quite slow on the newrelic monitoring website: > >>>>> > >>>>> Slowest Components Count Exclusive Total QueryElevationComponent 1 > >>>>> 506,858 ms 100% 506,858 ms 100% SolrIndexSearcher 1 2.0 ms 0% 2.0 ms > 0% > >>>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter() 1 1.0 ms 0% > >>>>> 506,862 > >>>>> ms > >>>>> 100% QueryComponent 1 1.0 ms 0% 1.0 ms 0% DebugComponent 1 0.0 ms 0% > 0.0 > >>>>> ms > >>>>> 0% FacetComponent 1 0.0 ms 0% 0.0 ms 0% > >>>>> > >>>>> As you could see, QueryElevationComponent takes quite a lot of time. > Any > >>>>> suggestion how to improve this? > >>>>> > >>>>> -- > >>>>> Chhorn Chamnap > >>>>> http://chamnapchhorn.blogspot.com/ > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> Chhorn Chamnap > >>>> http://chamnapchhorn.blogspot.com/ > >>>> > >>> > >>> > >>> -- > >>> Chhorn Chamnap > >>> http://chamnapchhorn.blogspot.com/ > >>> > >> > >> > >> > >> -- > >> Lance Norskog > >> goks...@gmail.com > >> > > > > > > -- > > Chhorn Chamnap > > http://chamnapchhorn.blogspot.com/ > > > > > > -- > Lance Norskog > goks...@gmail.com > -- Chhorn Chamnap http://chamnapchhorn.blogspot.com/
