Okay, if performance isn't the reason for the optimize, what is the reason
that you are using?
8GB for Java heap seems low for a 22GB index. How much Java heap seems
available when the app is running?
Are these three separate Solr instances/JVMs on the same machine?
How many cores for the machine?
-- Jack Krupansky
-----Original Message-----
From: Shawn Heisey
Sent: Tuesday, November 27, 2012 11:33 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr 4, optimizing while doing other updates?
On 11/27/2012 8:19 AM, Jack Krupansky wrote:
From your experience with your application, how big is the delta for query
time before and after a typical weekly optimize? 50%? 20%? 2%?
We've never tried to measure it. If I were chasing better performance,
I would be interested, but that's not the reason for the optimize. An
optimized index does *feel* faster than a freshly built one (DIH
full-import), but I have not recorded any numbers. With three 22GB
shards per server (64GB RAM, 8GB for java heap) and one server handling
the tiny shard as well, it's somewhat glacial whether there are 30
segments or 1.
Thanks,
Shawn
