Ok, have you a average size about the memory ocupation, by Solr ? You must to have a look about the really memory usage from cached fields, and try to set java memory to upper value
Are you evaluate the performance factors: http://wiki.apache.org/solr/SolrPerformanceFactors I think that is a memory problem, because when you issue queries that have few documents, its are load into memory (cache from solr) and the next queries don't use IO disk operation. But when the queries return too many documents, its can't be load in memory, by size, and for any query the solr must do load/unload memory operations, and disk reads ... Other cause can be the Lucene memory ocupation, but i need know what is the realy memory ocupation for the index. Sorry for my english :-( -----Mensaje original----- De: Jason Rennie [mailto:[EMAIL PROTECTED] Enviado el: jueves, 11 de septiembre de 2008 21:58 Para: solr-user@lucene.apache.org Asunto: Re: What's the bottleneck? On Thu, Sep 11, 2008 at 1:29 PM, <[EMAIL PROTECTED]> wrote: > what is your index configuration??? Not sure what you mean. We're using 1.2, though we've tested with a recent nightly and didn't see a significant change in performance... > What is your average size form the returned fields ??? Returned fields are relatively small, ~200 characters total per document. We're requesting the top 10 or so docs. How much memory have your System ?? 8g. We give the jvm a 2g (max) heap. We have another solr running on the same box also w/ 2g heap. The Linux kernel caches ~2.5g of disk. > Do you have long fieds who is returned in the queries ? No. The searched and returned fields are relatively short. One searched-over (but not returned) field can get up to a few hundred characters, but it's safe to assume they're all < 1k. > Do you have actÃvate the Highlighting in the request ? Nope. > Are you using multi-value filed for filter ... No, it does not have the multiValue attribute turned on. The qf field is just an integer. Any thoughts/comments are appreciated. Thanks, Jason
