Hi, Queries have to be rewritten, this has nothing to do with scoring. What type of queries are you seeing this? Wildcard or text ranges are expensive, there is no way around, but for MemoryIndex (I assume you mean this class), this should be quite cheap.
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: ppp.pawel...@gmail.com [mailto:ppp.pawel...@gmail.com] On > Behalf Of Pawel Rog > Sent: Monday, June 30, 2014 2:26 PM > To: java-user@lucene.apache.org > Subject: createNormalizedWeight > > Hi, > I'm running queries over memory index and see in profiler significant CPU > usage on method createNormalizedWeight. Most of the time is spent on > rewrite method. > > Is it any way to avoid it or optimize to reduce CPU usage on > createNormalizedWeight? Scoring is not important for me at all. It only want > to know if query matches do document or not. > > -- > Regards, > Paweł --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
