Hi,
1) Actually, I am not using Lucene directly, but a wrapper called
compass. I am using the find() method of the CompassSession, which code
is :
public CompassHits find(String query) throws CompassException {
return createQueryBuilder().queryString(query).toQuery().hits();
}
And all of these objects are pure wrappers around lucene equivalents,
nothing more.
2) What I am timing is only the find call :
-- start timer
CompassHits hits = compassSession.find("cityName:"+ name+"~");
-- stop timer
3) I am not sorting anything, but lucene is returning the hits by
relevance. Does this count as sorting ?
4) I tried to time the thing for ~10 queries, and the results are
roughly the same. Can go down to 2 seconds, which is still way too
much...
Thanks for helping
sami Dalouche
On Tue, 2006-05-30 at 13:58 -0700, Chris Hostetter wrote:
> : Fuzzy searching against this property takes around 3 seconds, which is
> : way too much for what I plan to do, so I am considering the possible
>
> whenever anyone has a question about how to speed up a search, and the
> current amount of time the search takes is more then a second, there are a
> few questions i allways want to ask:
>
> 1) what method exactly on the Searcher interface are you using the
> execute the search?
> 2) what exactly are you timing? (the time the search method call takes?,
> the time it takes you to iterate over the results? etc...)
> 3) are you sorting by any particular field?
> 4) are you reusing the Searcher instance for more then one query? are
> you timing more then one query and taking the average?
>
>
> -Hoss
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
