Return-Path: Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org Received: (qmail 84008 invoked from network); 4 Dec 2008 13:49:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2008 13:49:02 -0000 Received: (qmail 72025 invoked by uid 500); 4 Dec 2008 13:49:10 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 72005 invoked by uid 500); 4 Dec 2008 13:49:10 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 71994 invoked by uid 99); 4 Dec 2008 13:49:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2008 05:49:10 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates 209.85.198.234 as permitted sender) Received: from [209.85.198.234] (HELO rv-out-0506.google.com) (209.85.198.234) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Dec 2008 13:47:40 +0000 Received: by rv-out-0506.google.com with SMTP id f6so4934397rvb.5 for ; Thu, 04 Dec 2008 05:48:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=eLShX7Rjr0xr8qGqnYmTw64Q6pHPcyKlRdnxO2MHmoM=; b=m3VrM1+sZmZwnfsqardgB3M8/warz3+AmvYliD2s+Hn8SexLoDonbjdATmYkD1fA2e fVPSQg8ysq1dGuZpWhnogstMSJ2F7rIIrzKgVWNCHM0MEgVQzB/oQcqdAqr8V/cjDPXQ OWjLQyEaIXN9PV73StDHVyQSNiDLA2584RlSU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=ZnsloF+iWmiMyfKLvNHDfk3wOPiiH6uyFfL/lm32yPu1ejHKlDgQf7OjuI5kWtyyHD Tz2etV/qZEX28h/CUi9UVC9zfQm7Q38iyeHIndpU2rpVT7pFmrlr112DUvWopKuoFOZb FNiuKWf3BJ4dqT9ynnen9uWivQgnTr7wuDAXc= Received: by 10.140.136.5 with SMTP id j5mr6955017rvd.39.1228398498351; Thu, 04 Dec 2008 05:48:18 -0800 (PST) Received: by 10.141.212.15 with HTTP; Thu, 4 Dec 2008 05:48:18 -0800 (PST) Message-ID: Date: Thu, 4 Dec 2008 08:48:18 -0500 From: "Yonik Seeley" Sender: yseeley@gmail.com To: solr-user@lucene.apache.org Subject: Re: Resolr performance In-Reply-To: <20833521.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <866406203.20070219232142@yahoo.ca> <973395068.20070220104601@yahoo.ca> <20833521.post@talk.nabble.com> X-Google-Sender-Auth: f83701d24523d773 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Dec 4, 2008 at 8:36 AM, sunnyfr wrote: > When I check my CPU, all my CPU are not full, how can I change this ? If this is while you are indexing, then it simply means that you are not feeding documents to Solr fast enough (use multiple threads to send to Solr, and send multiple documents in each update request if possible). If CPU utilization is still low, then it means you are IO (disk) bound... if you want to go faster, get faster disks. -Yonik > Do I have to change a parameter ?? > > Thanks a lot , > Johanna > > > Walter Underwood wrote: >> >> Try running your submits while watching a CPU load meter. >> Do this on a multi-CPU machine. >> >> If all CPUs are busy, you are running as fast as possible. >> >> If one CPU is busy (around 50% usage on a dual-CPU system), >> parallel submits might help. >> >> If no CPU is 100% busy, the bottleneck is probably disk >> or network. >> >> wunder >> >> On 2/20/07 10:46 AM, "Jack L" wrote: >> >>> Thanks to all who replied. It's encouraging :) >>> >>> The numbers vary quite a bit though, from 13 docs/s (Burkamp) >>> to 250 docs/s (Walter) to 1000 docs/s I understand the results also >>> depend >>> on the doc size and hardware. >>> >>> I have a question for Erik: you mentioned "single threaded indexer" >>> (below). I'm not familiar with solr at all and did a search on solr >>> wiki for "thread" and didn't find anything. Is it so that I can >>> actually configure solr to be single-threaded and multi-threaded? >>> >>> And I'm not sure what you meant by parallelizing the indexer? >>> Running multiple instances of the indexer, or multiple instances >>> of solr? >>> >>> Thanks, >>> >>> Jack >>> >>>> My largest Solr index is currently at 1.4M and it takes a max of 3ms >>>> to add a document (according to Solr's console), most of them 1ms. >>>> My single threaded indexer is indexing around 1000 documents per >>>> minute, but I think I can get this number even faster by >>>> parallelizing the indexer. >>> >>> >>> __________________________________________________ >>> Do You Yahoo!? >>> Tired of spam? Yahoo! Mail has the best spam protection around >>> http://mail.yahoo.com >> >> >> > > -- > View this message in context: http://www.nabble.com/solr-performance-tp9055437p20833521.html > Sent from the Solr - User mailing list archive at Nabble.com. > >