search-benchmark-game
search-benchmark-game copied to clipboard
Search engine benchmark (Tantivy, Lucene, PISA, ...)
The k1 and b parameters of BM25 can influence what hits may be dynamically pruned and thus performance numbers, so it would be good to use the same values across...
Currently different engines use different parameters for BM25, e.g. Tantivy and Lucene use (k1=1.2,b=0.75) while PISA uses (k1=0.9,b=0.4). Robertson et al. had initially suggested that 1.2/0.75 would make good defaults...
It seems to me that the pisa-0.8.2 engine forces evaluation of all hits with the TOP_10_COUNT task, but it doesn't collect them into a priority queue as I would expect....
add new field id_num add range queries over id_num 
Like: - time to index - memory usage for indexing
Don't know if it's hard or not :/
https://github.com/luceneplusplus/LucenePlusPlus
Capture relevant hardware information (cpu type, Cache sizes, ...) and display it in the benchmark.