Hi Shawn, Here is the new screenshot of the Memory tab of the Resource Monitor. https://www.dropbox.com/s/w4bnrb66r16lpx1/Resource%20Monitor.png?dl=0
Yes, I found that the value under the "Working Set" column is much higher than the others. Also, the value which I was previously looking at under the Task Manager is under the Private Column here. It says that I have about 14GB of available memory, but the "Free" number is much lower, at 79MB. Regards. Edwin On 6 January 2016 at 03:11, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/5/2016 9:59 AM, Zheng Lin Edwin Yeo wrote: > > I have uploaded the screenshot here > > https://www.dropbox.com/s/l5itfbaus1c9793/Memmory%20Usage.png?dl=0 > > > > Basically, Java(TM) Platform SE Library, which Solr is running on, is > only > > using about 22GB currently. However, the memory usage at the top says it > is > > using 73% now (which I think is already higher than the figures, given > that > > I have 64GB of RAM), and it could potentially go up to 100%, even though > > the memory usage of Java(TM) Platform SE Library remains around 22GB, and > > there is no other new task which uses alot of memory are running. The > > figure is sorted according to the memory usage already. > > I would bet that the 73 percent refers to all memory allocated for *any* > purpose, including the disk cache. > > The screenshot that you provided is not the best way to see everything > that's happening in memory. With the task manager open, click on the > "Performance" tab, then click on "Open Resource Monitor" down at the > bottom of the window. This will open a whole new program. Once that's > open, click on the Memory tab, then click on the "Working Set" column > header to sort by that column. Increase the size of the window so that > a large number of processes with the memory utilization can be seen, > adjust the column widths so the information is clear, and make sure that > the "Physical Memory" graph and its legend are fully visible. Then grab > a new screenshot. > > I believe that you will find the "Available" number is quite high, even > though the "Free" number is very small ... and the difference will be > similar to the "Cached" number. If this is what you find, then > everything is working exactly as it is supposed to be working. > > Thanks, > Shawn > >
