I think the benchmarks need updating after LUCENE-8461. I got them working again by replacing lucene70 with lucene80 everywhere except for the DocValues formats, and adding the backward-codecs.jar to the benchmarks build. I'm not sure that was really the right way to go about this? After that I did try switching to use FST50 for this PKLookup benchmark (see below), but it did not recover the lost perf.
diff --git a/src/python/nightlyBench.py b/src/python/nightlyBench.py index b42fe84..5807e49 100644 --- a/src/python/nightlyBench.py +++ b/src/python/nightlyBench.py @@ -699,7 +699,7 @@ def run(): - idFieldPostingsFormat='Lucene50', + idFieldPostingsFormat='FST50', On Thu, Aug 23, 2018 at 5:52 PM Michael Sokolov <msoko...@gmail.com> wrote: > OK thanks. I guess this benchmark must be run on a large-enough index that > it doesn't fit entirely in RAM already anyway? When I ran it locally using > the vanilla benchmark instructions, I believe the generated index was quite > small (wikimedium10k). At any rate, I don't have any specific use case > yet, just thinking about some possibilities related to primary key lookup > and came across this anomaly. Perhaps at least it deserves an annotation on > the benchmark graph. >
