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 memory around as the heap expands, I usually set them both to the same value. How to determine what “the smallest heap you can” is? Unfortunately there’s no good way outside of stress-testing your application with less and less memory until you have problems, then add some extra… Best, Erick > On Sep 1, 2020, at 10:27 AM, Dominique Bejean <dominique.bej...@eolya.fr> > wrote: > > 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 mar. 1 sept. 2020 à 13:50, yaswanth kumar <yaswanth...@gmail.com> a > écrit : > >> 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 multiple >> times. Its like almost going to 95% (sometimes) and then coming down to 50% >> >> Solr version: 8.2 >> Zookeeper: 3.4 >> >> JVM size configured in solr.in.sh is min of 1GB to max of 10GB (actually >> RAM size on the node is 16GB) >> >> Basically need to understand if I need to worry about this heap % which >> was quite altering before making it live? or is that quite normal, because >> this is new UI change on solr cloud is kind of new to us as we used to have >> solr 5 version before and this UI component doesn't exists then. >> >> -- >> Thanks & Regards, >> Yaswanth Kumar Konathala. >> yaswanth...@gmail.com >> >> Sent from my iPhone
