This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This performance test loads the enwiki data set defined by
docs.file
in thecontent-source.properties
file.DocMaker
: https://lucene.apache.org/core/8_0_0/benchmark/org/apache/lucene/benchmark/byTask/feeds/DocMaker.htmlparses the xml files and creates ready to be indexed documents. Any wikipedia dataset downloaded from https://dumps.wikimedia.org/enwiki/20190501/ is usable as long as it is specified correctly in the properties file.
We can override the getContentSource to use other content sources:
https://lucene.apache.org/core/7_3_1/benchmark/org/apache/lucene/benchmark/byTask/feeds/ContentSource.html
for different benchmarking needs.
I left the
lucene-test-framework
library intact in our pom.xml because there are older performance benchmarks that still rely on it. We should remove it once we fully transition over to the lucene benchmark data setNext steps: