Dear Midas, Hi, AFAIK, currently Solr uses virtual memory for storing memory maps. Therefore using 36GB from 48GB of ram for Java heap is not recommended. As a rule of thumb do not access more than 25% of your total memory to Solr JVM in usual situations. About your main question, setting softcommit and hardcommit for Solr is highly dependent on your application. A really nice guide for this purpose is presented by lucidworks, In order to find the best value for softcommit and hardcommit please follow this guide: http://lucidworks.com/blog/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Best regards. On Mon, Nov 30, 2015 at 9:48 AM, Midas A <test.mi...@gmail.com> wrote: > Machine configuration > > RAM: 48 GB > CPU: 8 core > JVM : 36 GB > > We are updating 70 , 000 docs / hr . what should be our soft commit and > hard commit time to get best results. > > Current configuration : > <autoCommit> <maxTime>60000</maxTime> <openSearcher>false</openSearcher> </ > autoCommit> > > > <autoSoftCommit> <maxTime>600000</maxTime> </autoSoftCommit> > > There are no read on master server. > -- A.Nazemian
