Hi, with standard configuartion, this cannot happen. What merge policy do you use? This looks to me like a misconfigured merge policy or using the NoMergePolicy. With 3,000 segments, it will be slow, the question is, why do you get those?
Another thing could be: Do you always close IndexWriter after adding few documents and when closing, disable "wait for merge"? In that case, all merges are interrupted and the merge policy never has a chance to merge at all (because you are opening and closing IndexWriter all the time with cancelling all merges)? Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Scott Smith [mailto:ssm...@mainstreamdata.com] > Sent: Friday, March 15, 2013 11:15 PM > To: java-user@lucene.apache.org > Subject: Lucene slow performance > > We have a system that is using lucene and the searches are very slow. The > number of documents is fairly small (less than 30,000) and each document is > typically only 2 to 10 kilo-characters. Yet, searches are taking 15-16 > seconds. > > One of the things I noticed was that the index directory has several thousand > (3000+) .cfs files. We do optimize the index once per day. This is a system > that probably gets several thousand document deletes and additions per day > (spread out across the day). > > Any thoughts. We didn't really notice this until we went to 4.x. > > Scott > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
