You should _not_ set "-XX:G1HeapRegionSize=n" , because:
"... The goal is to have around 2048 regions based on the minimum Java heap
size"
The value of G1HeapRegionSize is automatically calculated upon start up of the
JVM.
The parameter "-XX:MaxGCPauseMillis=200" is the default.
Where is
That's good. I think I need to mention one other point about this
matter. It is feeding files into Tika (in my case) is paced to avoid
overloads. That is done in my crawler by having a small adjustable pause
(~100ms) after each file submission, and then longer ones (1-3 sec)
after every
I got some understanding now about my actual question.. thanks all for your
valuable theories
Sent from my iPhone
> On Sep 1, 2020, at 2:01 PM, Joe Doupnik wrote:
>
> As I have not received the follow-on message to mine I will cut
> it below.
> My comments on that are the numbers
This is misleading and not particularly good advice.
Solr 8 does NOT contain G1. G1GC is a feature of the JVM. We’ve been using
it with Java 8 and Solr 6.6.2 for a few years.
A test with eighty documents doesn’t test anything. Try a million documents to
get Solr memory usage warmed up.
GC_TUNE
You want to run with the smallest heap you can due to Lucene’s use of
MMapDirectory,
see the excellent:
https://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html
There’s also little reason to have different Xms and Xmx values, that just
means you’ll
eventually move a bunch of
Hi,
As all Java applications the Heap memory is regularly cleaned by the
garbage collector (some young items moved to the old generation heap zone
and unused old items removed from the old generation heap zone). This
causes heap usage to continuously grow and reduce.
Regards
Dominique
Le
Can someone make me understand on how the value % on the column Heap is
calculated.
I did created a new solr cloud with 3 solr nodes and one zookeeper, its not yet
live neither interms of indexing or searching, but I do see some spikes in the
HEAP column against nodes when I refresh the page
