Yes. I can guarantee that a force merge will not "massively help". It might not
even measurably help.
wunder
On Nov 4, 2012, at 1:05 PM, Otis Gospodnetic wrote:
> Measure / monitor first :)
> You may not need to optimize at all, especially if your index is always
> being modified.
>
> Otis
> -
Measure / monitor first :)
You may not need to optimize at all, especially if your index is always
being modified.
Otis
--
Performance Monitoring - http://sematext.com/spm
On Nov 4, 2012 3:03 PM, "tictacs" wrote:
> Thanks for the reply both and apologies if this is a recurring question.
> From t
Or, don't "optimize" (force merge) at all. Really. This is a manual override
for an automatic process, merging.
I can only think of one case where a forced merge makes sense:
1. All documents are reindexed.
2. Traditional Solr replication is used (not SolrCloud).
3. Replication is manually timed
Thanks for the reply both and apologies if this is a recurring question.
>From the sounds of it I am sure an optimize overnight when app traffic is
low will suffice. This will massively help with server perfomance I am
sure.
--
View this message in context:
http://lucene.472066.n3.nabble.com/
Hi,
This should become a FAQ. Short version: don't optimize. Check ML archives
for recent messages and explanations.
If you have a monitoring tool, look at disk io during and after
optimization, check solr cache hit rates, etc.
Otis
--
Performance Monitoring - http://sematext.com/spm
On Nov 3, 2
I'd recommend not optimizing every hour. Are you seeing a significant
performance increase from optimizing this frequently?
-Michael
