'Thread Limit in multiple app servers' is just a rumour from old prefork HTTPD. You can't maintain KeepAlive for 1024 concurrent internet users by having default 150 threads! On Windows platform, each thread needs 20Mb for execution stack, and this is the only limitation. On Apache HTTPD, each multithreaded worker process needs about 20Mb of RAM. Each thread listens to requests from specific TCP socket, and sometimes even sleeps.
I have 144 client threads in separate JVM, standalone JSE 5. Searching+Indexing+AutoCommit happens concurrently, and I have <add>s only _once_per_second_ (for the whole bunch of 144 client threads sleeping 7 seconds from 7.1!) I suspect "autocommit" setting... I didn't have any problem before. I need to check source code too... Thanks, Fuad -----Original Message----- From: Yonik Seeley [mailto:[EMAIL PROTECTED] Sent: Monday, January 29, 2007 11:20 PM To: [email protected] Subject: Re: Performance Tuning On 1/29/07, Fuad Efendi <[EMAIL PROTECTED]> wrote: > right before sending Email, I tried to check solr admin screen... something > happened... SOLR stopped itself! I can't even see process Id, and admin > screen does not work, but CPU is still 95%... - I couldn't tell from your previous emails if this box was indexing only, or indexing + searching. - if it's also involved in searching, it could be hitting the "multiple threads generating a fieldcache entry" issue. A thread dump will help tell. - there is a thread limit to most app servers, if all the threads are busy doing something else, that could possibly block admin access too. -Yonik
