Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 52844 invoked from network); 11 Mar 2011 08:51:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Mar 2011 08:51:09 -0000 Received: (qmail 96773 invoked by uid 500); 11 Mar 2011 08:51:06 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 96726 invoked by uid 500); 11 Mar 2011 08:51:06 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 96718 invoked by uid 99); 11 Mar 2011 08:51:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2011 08:51:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [91.121.16.47] (HELO ns23917.ovh.net) (91.121.16.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2011 08:50:59 +0000 Received: (qmail 1326 invoked by uid 508); 11 Mar 2011 09:02:06 -0000 Received: from unknown (HELO spotter-dclnx.intra.spotter.com) (88.182.17.109) by ns23917.ovh.net with AES256-SHA encrypted SMTP; 11 Mar 2011 09:02:06 -0000 Received: from techno by spotter-dclnx.intra.spotter.com with local (Exim 4.72) (envelope-from ) id 1Pxy4d-00066A-IA for java-user@lucene.apache.org; Fri, 11 Mar 2011 09:51:51 +0100 Date: Fri, 11 Mar 2011 09:51:51 +0100 From: David Causse To: java-user@lucene.apache.org Subject: Re: Is ConcurrentMergeScheduler useful for multiple running IndexWriter's? Message-ID: <20110311085151.GE9672@spotter-dclnx> Mail-Followup-To: David Causse , java-user@lucene.apache.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Mar 04, 2011 at 07:02:48AM -0800, Jason Rutherglen wrote: > ConcurrentMergeScheduler is tied to a specific IndexWriter, however if > we're running in an environment (such as Solr's multiple cores, and > other similar scenarios) then we'd have a CMS per IW. I think this > effectively disables CMS's max thread merge throttling feature? Hi, We've made the same statement, so we switched to SerialMergeScheduler, in our case lucene run in a managed container with lot of indexes and lot of of updates. In some cases we noticed the creation of too much short lived thread, (mostly due to a not so smart IW usage, the new NRT Reader helps in this way). A good idea would be MergeScheduler implementation that accept an application controlled thread pool, some sort of ExecutorServiceMergeScheduler. Regards. -- David Causse Spotter http://www.spotter.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org