On 6/4/07, Andy Goodell <[EMAIL PROTECTED]> wrote:
Currently our application implements a score cutoff by iterating through the
hits and then stopping once it reaches a hit whose score is below our
threshold. We'd like to optimize this (and avoid looking at the entire hits
when we don't need to)
Currently our application implements a score cutoff by iterating through the
hits and then stopping once it reaches a hit whose score is below our
threshold. We'd like to optimize this (and avoid looking at the entire hits
when we don't need to) by having the score cutoff applied when the hits ar
