You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Lucene912PostingsFormat on indexes whose storage efficiency is not critical. Likely index.codec is a good heuristic. Use cases that require batter space efficiency will have it set to best_compression. So if it is set to default is a good heuristic to use the stack Lucene912PostingsFormat.
This will ensure search use cases will benefit from the query time performance improvements that have been made overtime in Lucene's default postings format. For uses cases that rely on better storage efficiency we should keep using the ES812PostingsFormat and in a follow up develop new posting format that uses PFOR and take advantage of query time benefits (like #115021 describes). The latter a higher hanging fruit, then just using the stock Lucene912PostingsFormat that comes with Lucene 10.
The text was updated successfully, but these errors were encountered:
martijnvg
changed the title
Use Lucene912PostingsFormat on indexes whose storage efficiency is not critical (heuristic to be defined, e.g. when index.codec is default and source.mode is not synthetic?).
Use Lucene912PostingsFormat on indexes whose storage efficiency is not critical
Dec 19, 2024
martijnvg
changed the title
Use Lucene912PostingsFormat on indexes whose storage efficiency is not critical
Use 'Lucene912PostingsFormat' when storage efficiency is not critical
Dec 19, 2024
martijnvg
changed the title
Use 'Lucene912PostingsFormat' when storage efficiency is not critical
Use 'Lucene912PostingsFormat' when storage efficiency isn't critical
Dec 19, 2024
Use
Lucene912PostingsFormat
on indexes whose storage efficiency is not critical. Likelyindex.codec
is a good heuristic. Use cases that require batter space efficiency will have it set tobest_compression
. So if it is set todefault
is a good heuristic to use the stackLucene912PostingsFormat
.This will ensure search use cases will benefit from the query time performance improvements that have been made overtime in Lucene's default postings format. For uses cases that rely on better storage efficiency we should keep using the
ES812PostingsFormat
and in a follow up develop new posting format that uses PFOR and take advantage of query time benefits (like #115021 describes). The latter a higher hanging fruit, then just using the stockLucene912PostingsFormat
that comes with Lucene 10.The text was updated successfully, but these errors were encountered: