Also, reduce your commit frequency, if you are doing an initial import. You only need to commit (manually) once all of your content has been imported.
I gave a talk about this sort of thing last week at the Online Information Show in London, and am attempting to get the slides put online, when I can get access to the account I need to do it! Upayavira On Tue, 07 Dec 2010 11:36 +0100, "Peter Karich" <peat...@yahoo.de> wrote: > Hi Hamid, > > try to avoid autowarming when indexing (see solrconfig.xml: > caches->autowarm + newSearcher + maxSearcher). > If you need to query and indexing at the same time, > then probably you'll need one read-only core and one for writing with no > autowarming configured. > See: http://wiki.apache.org/solr/NearRealtimeSearchTuning > > Or replicate from the indexing-core to a different core with different > settings. > > Regards, > Peter. > > > > Hi, > > > > I am using multi-core tomcat on 2 servers. 3 language per server. > > > > I am adding documents to solr up to 200 doc/sec. when updating process is > > started, every thing is fine (update performance is max 200 ms/doc. with > > about > > 800 MB memory used with minimal cpu usage). > > > > After 15-17 hours it's became so slow (more that 900 sec for update), used > > heap > > memory is about 15GB, GC time is became more than one hour. > > > > > > I don't know what's wrong with it? Can anyone describe me what's the > > problem? > > Is that came from Solr or JVM? > > > > Note: when i stop updating, CPU busy within 15-20 min. and when start > > updating > > again i have same issue. but when stop tomcat service and start it again, > > all > > thing is OK. > > > > I am using tomcat 6 with 18 GB memory on windows 2008 server x64. Solr 1.4.1 > > > > thanks in advanced > > Hamid > > > -- > http://jetwick.com twitter search prototype > >
