LuXugang commented on code in PR #12405:
URL: https://github.com/apache/lucene/pull/12405#discussion_r1263421231
##
lucene/core/src/java/org/apache/lucene/search/TopDocs.java:
##
@@ -159,7 +159,12 @@ public MergeSortQueue(Sort sort, TopDocs[] shardHits,
Comparator tieBr
jpountz commented on issue #12439:
URL: https://github.com/apache/lucene/issues/12439#issuecomment-1635846764
Document frequencies have an impact indeed, but the logic would become quite
complicated wouldn't it?
Separately, by discussing about this with @jimczi, I realized that we may
datbates commented on issue #12424:
URL: https://github.com/apache/lucene/issues/12424#issuecomment-1636135349
That would work. Thanks for considering that.
By the way we have increased our Lucene performance to better than its
previous levels by introducing a full cache of our rec
almogtavor commented on issue #12406:
URL: https://github.com/apache/lucene/issues/12406#issuecomment-1636198608
Can someone take a look?
--
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 speci
gsmiller commented on PR #12417:
URL: https://github.com/apache/lucene/pull/12417#issuecomment-1636510014
Now for something possibly more useful. I brought the current vectorized
version of ForUtil from this PR over to the local Lucene fork we use for Amazon
product search and ran some inte
tang-hi commented on PR #12417:
URL: https://github.com/apache/lucene/pull/12417#issuecomment-1636640909
It's great to see the performance results in a production environment. May I
inquire if you employ the concept of lazy computation? If not, I believe it
would be a big enhancement to in
