I guess this is definitely due to the firstsearcher defined in solrconfig.xml, you must make some tweaks in that I hope it will help. We are using the same typo which you just mentioned here but we are using the indexing server separately and replicating data to our other two server so that it won't harm any search performance.
Thanks Aman Tandon On Thu, Apr 10, 2014 at 12:10 PM, Atanas Atanasov <atanaso...@gmail.com>wrote: > Hi, guys, > > I need some help. After updating to SOLR 4.4 the tomcat process is > consuming about 2GBs of memory, the CPU usage is about 40% after the start > for about 10 minutes. However, the bigger problem is, I have about 1000 > cores and seems that for each core a thread is created. The process has > more than 1000 threads and everything is extremely slow. Creating or > unloading a core even without documents takes about 20 minutes. Searching > is more or less good, but storing also takes a lot. > Is there some configuration I missed or that I did wrong? There aren't many > calls, I use 64 bit tomcat 7, SOLR 4.4, latest 64 bit Java. The machine has > 24 GBs of RAM, a CPU with 16 cores and is running Windows Server 2008 R2. > Index is uppdated every 30 seconds/10 000 documents. > I haven't checked the number of threads before the update, because I didn't > have to, it was working just fine. Any suggestion will be highly > appreciated, thank you in advance. > > Regards, > Atanas >
