Re: debugging IndexSearcher.search performance

[Kudrettin Güleryüz <ku...@gmail.com>]

Thanks for the response and sorry for not updating the thread. issue turned
out to be not related to IndexSearcher.search() Further looking in the
code, found that the method was called multiple times. Issue resolved after
refactoring.

Thanks,
Kudret

On Thu, Mar 10, 2016 at 2:03 AM Adrien Grand <jp...@gmail.com> wrote:

> There is a lot of things happening under this method. Since it seems that
> you ran this under a profiler, do you have a breakdown of which methods
> this CPU time is spent in?
>
> Le mar. 8 mars 2016 à 17:16, Kudrettin Güleryüz <ku...@gmail.com> a
> écrit :
>
> > Hi,
> >
> > The code I am working on is spending long time in this function:
> > Searcher.java:221 org.apache.lucene.search.IndexSearcher.search(Query,
> int,
> > Sort) 94400ms 95%
> >
> > Query fed to the function looks ugly at first and I first thought that it
> > could be the culprit:
> > +body:/.*foo/ +((+dir1:foo +dir2:bar) (+dir1:baz) (+dir1:bin) ...(the
> list
> > goes on for all top level directories indexed. For a total of ~60
> > directories))
> >
> > However same query completes much faster in Luke. It shouldn't be because
> > of Sort either because it takes long time for no matches, too.
> >
> > Any suggestions while I debug this issue?  Lucene 5 is what I am using
> > currently.
> >
> > Thanks,
> > Kudret
> >
>