[ http://issues.apache.org/jira/browse/LUCENE-443?page=comments#action_12331735 ]
paul.elschot commented on LUCENE-443: ------------------------------------- The score() method can be simplified to use only the 'i' index. There is no need to offset the index into the scorers with the 'pos' variable, because all scorers match. Regards, Paul Elschot > ConjunctionScorer tune-up > ------------------------- > > Key: LUCENE-443 > URL: http://issues.apache.org/jira/browse/LUCENE-443 > Project: Lucene - Java > Type: Bug > Components: Search > Versions: 1.9 > Environment: Linux, Java 1.5, Large Index with 4 million items and some > heavily nested boolean queries > Reporter: Abdul Chaudhry > Attachments: ConjunctionScorer.java, ConjunctionScorer.java > > I just recently ran a load test on the latest code from lucene , which is > using a new BooleanScore and noticed the ConjunctionScorer was crunching > through objects , especially while sorting as part of the skipTo call. It > turns a linked list into an array, sorts the array, then converts the array > back to a linked list for further processing by the scoring engines below. > 'm not sure if anyone else is experiencing this as I have a very large index > (> 4 million items) and I am issuing some heavily nested queries > Anyway, I decide to change the link list into an array and use a first and > last marker to "simulate" a linked list. > This scaled much better during my load test as the java gargbage collector > was less - umm - virulent -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
