lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <>
Subject Re: High cpu and gc time when performing optimization.
Date Tue, 12 Jul 2016 14:14:07 GMT
Optimize is a very expensive operation.  It involves reading the
entire index and merging and rewriting at a single segment.
If you find it too expensive, do it less often, or don't do it at all.
It's an optional operation.


On Mon, Jul 11, 2016 at 10:19 PM, Jason <> wrote:
> hi, all.
> I'm running solr instance with two cores and JVM max heap is 32G.
> Each core index size is 68G, 61G repectively.
> I'm always keeping on optimization after update index.
> BTW, on last week, document update is completed but optimize phase cpu is
> very high.
> I think that is because long gc time.
> How should I solve this problem?
> welcome any idea.
> thanks,
> --
> View this message in context:
> Sent from the Solr - User mailing list archive at

View raw message