mikemccand commented on issue #16574: URL: https://github.com/apache/lucene/issues/16574#issuecomment-5478742993
I like this idea! The expected and actual (in full enwiki luceneutil benchmarks) gains are due to locality of terms-heavy work (finding or adding a term during inversion, sorting for flush)? The `byte[]` block allocator is still shared between the two, right? It's just that in each block we would write only terms' UTF-8 bytes, or only postings, never mixing. Thank you for the deep analysis / benchmarking / flame charts dev eye candy! You might see even more gains if you turn on term vectors (<-- very confusingly named (long ago) Lucene feature!), which is a baby inverted index per document that is also looking up terms and assigning ordinals via document-private-and-reused `TermsHash` I think. -- 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 specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
