lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3262) Facet benchmarking
Date Sun, 09 Oct 2011 09:36:29 GMT


Shai Erera commented on LUCENE-3262:

bq. Those number are scenario dependent but I think most cases I encountered are closer to
my proposed numbers

I think we should maybe have a Wiki page or something with several .alg files that test different
scenarios. I don't think that 1-120 is an example we shouldn't test. Rather, we should describe,
either in a Wiki or a JIRA issue, the performance results for each scenario. And if the results
are suspicious for a particular scenario, dig deeper and understand why.

So given that you know the numbers from above were run with that many facets per document,
do the numbers make sense? Or you still think they're high?

bq. I would suggest renaming max.facet.length (in the alg) & maxFacetLengh (in the code)
to max.facet.depth and maxFacetDepth

> Facet benchmarking
> ------------------
>                 Key: LUCENE-3262
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: modules/benchmark, modules/facet
>            Reporter: Shai Erera
>            Assignee: Doron Cohen
>         Attachments:, LUCENE-3262.patch, LUCENE-3262.patch, LUCENE-3262.patch,
> A spin off from LUCENE-3079. We should define few benchmarks for faceting scenarios,
so we can evaluate the new faceting module as well as any improvement we'd like to consider
in the future (such as cutting over to docvalues, implement FST-based caches etc.).
> Toke attached a preliminary test case to LUCENE-3079, so I'll attach it here as a starting
> We've also done some preliminary job for extending Benchmark for faceting, so I'll attach
it here as well.
> We should perhaps create a Wiki page where we clearly describe the benchmark scenarios,
then include results of 'default settings' and 'optimized settings', or something like that.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message