tantivy document memory experiment #2371
Open
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.
Some test regarding the memory consumption of
TantivyDocument
Experiment
Parse data set lines and store all Documents in a
Vec
.hdfs: 3 fields (timestmap, body, severity), raw dataset
22MB
gh: all fields in a json field (dynamic mode). raw dataset
2.3MB
Note: The root level in
hdfs
fields are stored as Field id instead as stringVariant1: TantivyDocumentMedVec
replace
Vec
in OwnedValue with 32 bit versions of the Vec and drop Facet and PretokstrVariant2: DocContainerRef
The nodes all store their data in 2 vecs and just reference the position there
Results
Conclusion
There should be some easy gains by using 32 bit vecs, which only use 16byte instead of 24 bytes.
DocContainerRef
could provide additional gains, but adds some complexity.quickwit-oss/quickwit#4890