Does it need 10G to run? Have you cycled it down to, say, 4-5G as a test? Large memory sizes can just cause more garbage collection.
What is the disk activity when this happens? Do you have paging turned on? I generally turn it off- having things go into page-thrash mode is lame. How many searchers are open? With commits that quick, you might be building up old searches which hold their data index data open. On Thu, Nov 18, 2010 at 5:49 PM, Simon Wistow <si...@thegestalt.org> wrote: > On Fri, Nov 19, 2010 at 12:01:09AM +0000, me said: >> I'm baffled - I've had way bigger indexes than this before with no >> performance problems. At first it was the frequent updates but the fact >> that it happens even when the indexer isn't running seems to put paid to >> that. > > More information: > > - The index has ~30 million smallish documents > > - Once a slow query has been executed all other queries, even ones which > had previously been slow but tolerable (response times ~1s) become > incredibly slow > > - Once the process has turned slow only a kill -9 will bring it down > > - Upgrading to a recent nightly build of Solr (3.1-2010-11-18_05-27-29 > 1036325 - hudson - 2010-11-18 05:41:58) has made things even slower > > - I'd check with 4.0.x if someone can point me at a tool that can > migrate indexes. I seem to be unable to find one and Lucene 3.0 informs > me that it's incompatible with 2.9.x > > > > > > > > -- Lance Norskog goks...@gmail.com
