bruno-roustant commented on pull request #430: URL: https://github.com/apache/lucene/pull/430#issuecomment-969337494
Woah, @jpountz your idea has a clear effect. It brings +(10 - 12)% perf, compared without the top-k optim. And top-k optim adds another +3% on top (plus it is still very effective for k very close to boundaries). So I'd like to keep both. I hope it does not make the code too complex. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
