Li Li [mailto:fancye...@gmail.com]
Sent: Thursday, March 17, 2011 10:38 PM
To: solr-user@lucene.apache.org
Subject: Re: Helpful new JVM parameters
will UseCompressedOops be useful? for application using less than 4GB
memory, it will be better that 64bit reference. But for larger memory
using applica
will UseCompressedOops be useful? for application using less than 4GB
memory, it will be better that 64bit reference. But for larger memory
using application, it will not be cache friendly.
"JRocket the definite guide" says: "Naturally, 64 GB isn't a
theoretical limit but just an example. It was me
Awesome, very helpful. Do you maybe want to add this to the Solr wiki
somewhere? Finding some advice for JVM tuning for Solr can be
challenging, and you've explained what you did and why very well.
On 3/17/2011 2:59 PM, Dyer, James wrote:
We're on the final stretch in getting our product data
We're on the final stretch in getting our product database in Production with
Solr. We have 13m "wide-ish" records with quite a few stored fields in a
single index (no shards). We sort on at least a dozen fields and facet on
20-30. One thing that came up in QA testing is we were getting full
