[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-user
Subject:    Re: debugging IndexSearcher.search performance
From:       Adrien Grand <jpountz () gmail ! com>
Date:       2016-03-10 7:03:39
Message-ID: CAPsWd+OnOAYwsC6TAoJZOz9_Xx=BxHyXeqkFfCFcFX4KKARbvA () mail ! gmail ! com
[Download RAW message or body]


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 =C3=A0 17:16, Kudrettin G=C3=BClery=C3=BCz <kudrettin@g=
mail.com> a
=C3=A9crit :

> Hi,
>
> The code I am working on is spending long time in this function:
> Searcher.java:221 org.apache.lucene.search.IndexSearcher.search(Query, in=
t,
> 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 lis=
t
> 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
>


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic