Hi Ameya, Tough to say without more information about what's slow. In general, when I've seen Solr index that slow, it's usually related to some complex text analysis, for instance, are you doing any phonetic analysis? Best thing to do is attach a Java profiler (e.g. JConsole or VisualVM) using rmi and see where the hotspots are (this will also give you hints about GC activity).
Here are the flags I use to setup my Solr server to allow JConsole or VisualVm to attach. You can also try out YourKit (it's better but a little more involved to use). -Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.local.only=false \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote.port=1084 \ -Dcom.sun.management.jmxremote.rmi.port=1084 -Djava.rmi.server.hostname=$SOLR_HOST Note: Have a chat with your sysadmin about these before using in production ;-) On Tue, Jul 29, 2014 at 11:49 AM, Ameya Aware <ameya.aw...@gmail.com> wrote: > Hi, > > I am running Solr with below parameters: > > -XX:MaxPermSize=128m -Xms5120m -Xmx5120m -XX:+UseConcMarkSweepGC > -XX:CMSInitiatingOccupancyFraction=70 -XX:NewRatio=3 > -XX:MaxTenuringThreshold=8 -XX:+CMSParallelRemarkEnabled > -XX:+ParallelRefProcEnabled -XX:+UseLargePages -XX:+AggressiveOpts > -XX:-UseGCOverheadLimit > > > I need to index around 300000 documents but with above parameters > performance is coming very poor around 15000-20000 documents per hour. > > This would take a lot of time to index all the documents. > > Also, my autocommit in solrconfig.xml is as below: > > <autoCommit> > <maxTime>150000</maxTime> > <openSearcher>false</openSearcher> > </autoCommit> > > <documentCache class="solr.LRUCache" autowarmCount="0" initialSize="256" > size="256"/> > > > > I am running Solr on machine having 12GB RAM. > > > Please advice on how can i improve the performance. > > > Thanks, > Ameya
