Thomas Becker wrote: > Here's the results of profiling 10 different search requests: > > http://ankeschwarzer.de/tmp/lucene_24_oldapi.png > http://ankeschwarzer.de/tmp/lucene_29_oldapi.png > http://ankeschwarzer.de/tmp/lucene_29_newapi.png > > But you already gave me a good hint. The index being used is an old one build > with lucene 2.4. I will now try a freshly build 2.9 index and see if > performance > improves. Maybe that already solves the issue...stupid me... > That shouldn't be an issue unless there is some odd bug.
> We're updating the index every 30 min. at the moment and it gets optimized > after > each update. > So this profiling is on an optimized index (eg a single segment) ? That would be odd indeed, and possibly point to some of the scoring changes. > > Mark Miller wrote: > >> Thomas Becker wrote: >> >>> Hey Mark, >>> >>> thanks for your reply. Will do. Results will follow in a couple of minutes. >>> >>> >>> >>> >> Thanks, awesome. >> >> Also, how many segments (approx) are in your index? If there are a lot, >> have you/can you try the same tests on an optimized index? Don't want to >> get ahead of the profiling results, but just to continue the info loop. >> >> > > -- - Mark http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
