Hi Mikhail,
is this, what you've requested?
lookups: 34084
hits: 34067
hitratio: 1
inserts: 34
evictions: 0
...
item_author_facet:
{field=author_facet,memSize=104189615,tindexSize=789195,time=16901,phase1=16534,nTerms=3989851,bigTerms=0,termInstances=16214154,uses=4065}
item_topic_facet:
{field=topic_facet,memSize=103817915,tindexSize=112199,time=8912,phase1=8496,nTerms=525261,bigTerms=0,termInstances=11050466,uses=1510}
item_material_access:
{field=material_access,memSize=4532,tindexSize=46,time=1820,phase1=1820,nTerms=2,bigTerms=2,termInstances=0,uses=3406}
(The fields 'author_facet' and 'topic_facet' do have a lot of unique
entries. 'material_access' has only two values ('online' vs. 'print')
Beside of "*:*", querys with more than maxdoc/2 hits happen very very
rawly. Typical requests results in less than 1% of maxdoc.
Here a typical example, searching for "Goethe" in the portfolio of the
University Library Frankfurt/Main
> https://hds.hebis.de/ubffm/Search/Results?lookfor=goethe&search=new
The request yields over 31,000 results (~.2%. of maxdocs). The majority
are books about Goethe, 'just' 5700 books are from him. The facet helps
to detect professionals.
Like Walter Underwood wrote, in technical sense faceting on authors
isn't a good idea. In the worst case, the relation book to author is
n:n. Never the less, thanks to authority files (which are intensively
used in Germany) the facet 'author' is often helpful.
Uwe
Am 26.09.2015 um 14:08 schrieb Mikhail Khludnev:
Uwe,
Would you mind to provide a few details about your case?
I wonder about number of bigterms and other stats as well at 'author' field
(ant other most expensive facets). It looks like log rows:
Sep 13, 2011 2:51:53 PM org.apache.solr.request.UnInvertedField uninvert
INFO: UnInverted multi-valued field
{*field=nomejornal*,memSize=827108,tindexSize=40,time=16,phase1=4,*nTerms=15,bigTerms=0*,termInstances=750,uses=0}
Those heavy requests, do they find more than half of docs, eg hits>maxdoc/2 ?
Thanks for your input!
On Thu, Sep 24, 2015 at 11:38 AM, Uwe Reh <r...@hebis.uni-frankfurt.de>
wrote:
Am 22.09.2015 um 18:10 schrieb Walter Underwood:
Faceting on an author field is almost always a bad idea. Or at least a
slow, expensive idea.
Hi Wunder,
n a technical context, the 'author'-facet may be suboptimal. In our
businesses (library services) it's a core feature.
Yes the facet is expensive, but thanks to the fieldValueCache (4.10)
sufficiently fast.
uwe
