On 4/12/2012 12:42 PM, Rohit wrote:
Thanks for pointing these out, but I still have one concern, why is the Virtual Memory running in 300g+?
Solr 3.5 uses MMapDirectoryFactory by default to read the index. This does an mmap on the files that make up your index, so their entire contents are simply accessible to the application as virtual memory (over 300GB in your case), the OS automatically takes care of swapping disk pages in and out of real RAM as required. This approach has less overhead and tends to make better use of the OS disk cache than other methods. It does lead to confused questions and scary numbers in memory usage reporting, though.
You have mentioned that you are giving 36GB of RAM to Solr. How much total RAM does the machine have?
Thanks, Shawn
