> > I already posted a while ago a problem that one of the solr threads > > starts using 100% of one of the processor cores on a 4 core > > system. > > This sounds like warming / autowarming. > The other possibility is garbage collection.
What can I do here? Decrease the autowarmcount? My current settings filterCache autowarmCount="256" queryResultCache autowarmCount="256" documentCache autowarmCount="0" > > This doesn't happen right after the start it slightly > > increaes for about a week until the process runs constantly at > > 100%. > > Is it still just one CPU at 100%, or is it ever 2 or more at 100%. > That would tell us if it were due to overlapping autowarming. It is always just one core. All the other cores run once in a while at 100% but only one core is constantly at 100% > What happens to your index over time? Does maxDoc() keep increasing? Yes maxDoc is always increasing it is pretty much the same as the total number of indexed documents. > Perhaps post the XML you get from the statistics page so we might > know more. Try looking in the logs to see what part of autowarming is > taking so long. While checking the logs I run over some performance warnings. I run a optimize every night. Minutes after I start the optimize I get a: INFO: PERFORMANCE WARNING: Overlapping onDeckSearchers=2 Could the problem be related to this? I disabled the optimize for now. If the optimize is the problem what would be a better different strategy to run the optimize? Thanks for your help. Cheers, Michael -- Michael Thessel <[EMAIL PROTECTED]> Gossamer Threads Inc. http://www.gossamer-threads.com/ Tel: (604) 687-5804 Fax: (604) 687-5806
