StatsComponent, like many things, relies on FieldCache (and the related uninverted version in Solr for multivalued fields), which takes up memory and is related to the number of documents in the index. Strings in FieldCache can also be expensive.
-Grant On Jan 10, 2011, at 4:10 PM, Jonathan Rochkind wrote: > I found StatsComponent to be slow only when I didn't have enough RAM > allocated to the JVM. I'm not sure exactly what was causing it, but it was > pathologically slow -- and then adding more RAM to the JVM made it incredibly > fast. > > On 1/10/2011 4:58 AM, Gora Mohanty wrote: >> On Mon, Jan 10, 2011 at 2:28 PM, stockii<st...@shopgate.com> wrote: >>> Hello. >>> >>> i`m using the StatsComponent to get the sum of amounts. but solr >>> statscomponent is very slow on a huge index of 30 Million documents. how can >>> i tune the statscomponent ? >> Not sure about this problem. >> >>> the problem is, that i have 5 currencys and i need to send for each currency >>> a new request. thats make the solr search sometimes very slow. =( >> [...] >> >> I guess that you mean the search from the front-end is slow. >> >> It is difficult to make a guess without details of your index, >> and of your queries, but one thing that immediately jumps >> out is that you could shard the Solr index by currency, and >> have your front-end direct queries for each currency to the >> appropriate Solr server. >> >> Please do share a description of what all you are indexing, >> how large your index is, and what kind of queries you are >> running. I take it that you have already taken a look at >> http://wiki.apache.org/solr/SolrPerformanceFactors >> >> Regards, >> Gora >> -------------------------- Grant Ingersoll http://www.lucidimagination.com/
