I've seen even longer commit times with our 2GB index and have not had a chance to look into it deeper. What I have noticed is when there are Searchers registered commits take a lot longer time. Perhaps looking at the optional attributes for commit (waitSearcher, waitFlush) would help.
Since we use post.jar I believe the <commit/> command is not modifiable ie. waitSearcher=true, waitFlush=true are assumed. (Can someone confirm this?) -Andrew -----Original Message----- From: Lance Norskog [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 21, 2007 12:44 AM To: solr-user@lucene.apache.org Subject: Commit performance How long should a <commit> take? I've got about 9.8G of data for 9M of records. (Yes, I'm indexing too much data.) My commits are taking 20-30 seconds. Since other people set the autocommit to 1 second, I'm guessing we have a major mistake somewhere in our configurations. We have a lot of deletes/re-adds to commit. Any hints? Thanks, Lance
