Hi Toke, I read the server's memory usage from the Task manager under Windows,
Regards, Edwin On 4 January 2016 at 17:17, Toke Eskildsen <t...@statsbiblioteket.dk> wrote: > On Mon, 2016-01-04 at 10:05 +0800, Zheng Lin Edwin Yeo wrote: > > A) Before I start the optimization, the server's memory usage > > is consistent at around 16GB, when Solr startsup and we did some > searching. > > How do you read this number? > > > However, when I click on the optimization button, the memory usage > > increases gradually, until it reaches the maximum of 64GB which the > server > > has. > > There are multiple ways of looking at memory. The most relevant ones in > this context are > > - Total memory on the system > This appears to be 64GB. > > - Free memory on the system > Usually determined by 'top' under Linux or Task Manager under Windows. > > - Memory used for caching on the system > Usually determined by 'top' under Linux or Task Manager under Windows. > > - JVM memory usage > Usually determined by 'top' under Linux or Task Manager under Windows. > Look for "Res" (resident) for the task in Linux. It might be called > "physical" under Windows. > > > - Maximum JVM heap (Xmx) > Lightest grey in "JVM-Memory" in the Solr Admin interface Dashboard. > > - Allocated JVM heap (Xmx) > Medium grey in "JVM-Memory" in the Solr Admin interface Dashboard. > > - Active JVM heap (Xmx) > Dark grey in "JVM-Memory" in the Solr Admin interface Dashboard. > > > I am guessing that the number you are talking about is "Free memory on > the system" and as Shawn and Erick points out, a full allocation there > is expected behaviour. > > What we are interested in are the JVM heap numbers. > > - Toke Eskildsen, State and University Library, Denmark > > >
