You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Tjianke (via GitHub)" <gi...@apache.org> on 2023/03/01 08:52:01 UTC
[GitHub] [lucene] Tjianke commented on issue #11707: Re-evaluate different ways to encode postings [LUCENE-10672]
Tjianke commented on issue #11707:
URL: https://github.com/apache/lucene/issues/11707#issuecomment-1449598942
Lucene community has the good tradition of incorporating academic results. Recent studies show many efficient algorithms like [Partitioned Elias-Fano](http://groups.di.unipi.it/~ottavian/files/elias_fano_sigir14.pdf). Here's a great [paper ](https://arxiv.org/abs/1908.10598)comparing the space-time trade-off of various index compression. I'm interested in evaluating current codec and implementing state-of-art compressions if viable. But I'm new to Lucene, which aspects (index size/query speed/memory/CPU) do we need to evaluate? Is there any mature benchmark to exploit, I noticed a LuceneBenchmark repo though.
--
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: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org