On 12/8/06, Andrew Nagy <[EMAIL PROTECTED]> wrote:
Chris Hostetter wrote:
>: Could you suggest a better configuration based on this?
>
>If that's what your stats look like after a single request, then i would
>guess you would need to make your cache size at least 1.6 million in order
>for it to be of any use in improving your facet speed.
>
>
Would this have any strong impacts on my system? Should I just set it
to an even 2 million to allow for growth?
Change the following in solrconfig.xml, and you should be fine with a
higher setting.
<useFilterForSortedQuery>true</useFilterForSortedQuery>
to
<useFilterForSortedQuery>false</useFilterForSortedQuery>
That will prevent the filtercache from being used for anything but
filters and faceting, so if you set it to high, it won't be utilized
anyway.
>: My data is 492,000 records of book data. I am faceting on 4 fields:
>: author, subject, language, format.
>: Format and language are fairly simple as their are only a few unique
>: terms. Author and subject however are much different in that there are
>: thousands of unique terms.
>
>by the looks of it, you have a lot more then a few thousand unique terms
>in those two fields ... are you tokenizing on these fields? that's
>probably not what you want for ields you're going to facet on.
>
>
All of these fields are set as "string" in my schema
Are they multivalued, and do they need to be.
Anything that is of type "string" and not multivalued will use the
lucene FieldCache rather than the filterCache.
-Yonik
