Just set Xms and Xmx the same. The server will be running for weeks,
so allocate the memory and get on with it.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Oct 3, 2019, at 11:38 AM, ndra wrote:
>
>> I don’t think having the initial heap larger
> I don’t think having the initial heap larger than the max heap is a legal
configuration.
> I have no idea what that would do.
Sorry my wording was poor. I meant if, instead of my initial HEAP of 512MB,
it was closer to say 6 or 8GB or equal to my Max allowed of 10GB.
Appreciate the info
I don’t think having the initial heap larger than the max heap is a legal
configuration.
I have no idea what that would do.
Modern GCs have a separate area for short-lived allocations. When that fills up,
a minor GC happens. As allocations survive several minor GCs, they are moved
to the
> When the heap is out of free space that
>can be recovered with minor GC, the JVM will increase the size if possible.
>Once it is at max, it will do a major GC.
Thanks Walter,
One more quick question about the above, so if the initial HEAP was larger
(or equal to the max as you suggested
> On Oct 3, 2019, at 9:31 AM, ndra wrote:
>
> I was under the impression that by allocating a smaller initial HEAP I
> could avoid having a larger GCs but if I am understanding what you all are
> suggesting, the smaller initial HEAP is requiring more full GCs to maintian
> a HEAP closer to
Thank you all for the responses. I do have a question about moving to G1.
Is there any plans for SOLR to make this the default JAVA_OPT for SOLR? We
have been running CMS without any issue prior to 7.
The primary change we made between 6->7 was to increase the max HEAP size
and increase the Xms
As the others said: move to the newer GC. I would also use this opportunity to
work with the default Java options of Solr 7 and then tune again. If you change
major versions you should always review the GC settings if they still make
sense.
> Am 02.10.2019 um 23:14 schrieb Solr User :
>
>
Always make Xmx and Xms the same. The heap will increase to the max before a
major GC, so avoid the pauses to grow it.
Use the G1 collector. CMS is really obsolete. We’ve had G1 in prod for at least
three years.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my
Hi concerned (please use signature),
The timeouts could be because of the "stop the world" kinda behaviour of
longer GC pause. When we shifted our Auto-Suggest from Redis to Solr, I
faced the similar GC pause issue while stress testing. This article
Hello all,
We recently moved to SOLR 7 from SOLR 6 about 2 weeks ago. Once each week
(including today) we experienced query timeout issues with corresponding GC
events. There was a spike in CPU up to 66% which is not something we
previously saw w/ Solr 6. From the SOLR logs it looks like
Hello all,
We recently moved to SOLR 7 from SOLR 6 about 2 weeks ago. Once each week
(including today) we experienced query timeout issues with corresponding GC
events. There was a spike in CPU up to 66% which is not something we
previously saw w/ Solr 6. From the SOLR logs it looks like
11 matches
Mail list logo
