Hi Richard, > An attempt to add a single document and commit is taking many minutes but the > time taken is not consistent.
Are you committing after every doc? If so, don't do it. :) Check Solr ML archives (e.g. http://search-lucene.com/ ) for past discussions on this topic. Do you have any sort of Solr and server monitoring from which you can share any numbers/observations? If not, see http://sematext.com/spm Some questions to help: * version of Java * heap size and other JVM params * RAM size * disk IO before and during indexing * CPU usage before and during indexing * commit frequency * ... Otis ---- Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm >________________________________ > From: "richard.pog...@holidaylettings.co.uk" > <richard.pog...@holidaylettings.co.uk> >To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> >Sent: Wednesday, May 9, 2012 9:01 AM >Subject: Solr Performance > >Afternoon, > >We are testing an updated version of our Solr server running solr 3.5.0 and we >are experiencing some performance issues with regard to updates and commits. > >Searches are working well. > >There are approximately 80,000 documents and the index is about 2.5 GB. This >does not seem to be extreme based on other implementations I have seen. > >An attempt to add a single document and commit is taking many minutes but the >time taken is not consistent. > >Despite being in very light usage the java process seems to consistently >require an entire CPU core. > >Optimising the index produced a limited improvement but this also takes a good >deal of time to run. > >I am at a slight loss as to what the issue may be, I am interested in what >others think would be a normal commit time with this sort of data volume. > >I am thinking there may be an issue with the schema but I am just guessing. > >Many thanks for any help. > >Richard > > > > >
