I think what you are experiencing is just due to how the JVM works: it happily reserves memory to the operating system if it thinks it might need it, and then it's reluctant to give it back because it assumes that if it has needed so much memory in the past, it might need it again in the future. If you don't want to JVM to use so much memory, just pass a lower value of the maximum heap size.
On Wed, Apr 3, 2019 at 4:11 PM thturk <tahatur...@hotmail.com> wrote: > > I have tried Java VisualVM too watch GC status per each commit and relase > variables for Reader Writer Searcher. But as result GC working like in > photo at below > <http://lucene.472066.n3.nabble.com/file/t494233/Ekran_Al%C4%B1nt%C4%B1s%C4%B1.png> > After 16.40 I called GC manully but Heap size didnt decrease is it cos its > take while to merge serment for lucene ? cos after a hour Memory Ussage > Decreased around 3G it was 3.5G after add new 15k document. > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Lucene-Java-Users-f532864.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > -- Adrien --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
