Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 44284 invoked from network); 31 Aug 2010 03:35:04 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 31 Aug 2010 03:35:04 -0000 Received: (qmail 99997 invoked by uid 500); 31 Aug 2010 03:35:02 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 99659 invoked by uid 500); 31 Aug 2010 03:34:59 -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 99651 invoked by uid 99); 31 Aug 2010 03:34:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Aug 2010 03:34:58 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anithian@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-iw0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Aug 2010 03:34:53 +0000 Received: by iwn9 with SMTP id 9so7227626iwn.35 for ; Mon, 30 Aug 2010 20:34:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=qAiitCacDJVGsZTYdzWTred1lb1PMXzByYeZkMC0tt8=; b=mZvu9qk1a/crlumiJCdWRqh4PaCR67UUaM5Z2l5mlPIAsR1byAanrTfqalpbNJzKS8 ZOWqEwEZoFSiHYjoDhIZI1WUK5Miv+JdWsml2jkUd8iMR06PU84nrpChLezVfhqc1/za D0v7jLoS9PjENuifERjT6g06vkyMRA2S1mFG4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=N3dkK268yvJFDGClxA2IkB/y6TPD1kyPXeC1IFWXG4Ig2qP0SL5WjSiGsPPZlYI7dO 3ZR1pb9jgxYen0RbkI6dfiB/To8etW9fJfOgQqWXP/ihc5MNlk0nROWt4nx8ZGBOUaeJ 2YBfD03fEZ+1/tmZfJks77FwFoesEB/D5OZmU= Received: by 10.231.79.77 with SMTP id o13mr6568731ibk.36.1283225673144; Mon, 30 Aug 2010 20:34:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.144.199 with HTTP; Mon, 30 Aug 2010 20:34:13 -0700 (PDT) In-Reply-To: <1957FC4418E54F29BF7545C64017F545@udc70634P002> References: <1957FC4418E54F29BF7545C64017F545@udc70634P002> From: Amit Nithian Date: Mon, 30 Aug 2010 20:34:13 -0700 Message-ID: Subject: Re: Hardware Specs Question To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=001485f872ca6a1868048f164243 --001485f872ca6a1868048f164243 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Lance, makes sense and I have heard about the long GC times on large heaps but I personally haven't experienced a slowdown but that doesn't mean anything either :-). Agreed that tuning the SOLR caching is the way to go. I haven't followed all the solr/lucene changes but from what I remember there are synchronization points that could be a bottleneck where adding more cores won't help this problem? Or am I completely missing something. Thanks again Amit On Mon, Aug 30, 2010 at 8:28 PM, scott chu (=E6=9C=B1=E7=82=8E=E8=A9=B9) wrote: > I am also curious as Amit does. Can you make an example about the garbage > collection problem you mentioned? > > ----- Original Message ----- From: "Lance Norskog" > To: > Sent: Tuesday, August 31, 2010 9:14 AM > Subject: Re: Hardware Specs Question > > > > It generally works best to tune the Solr caches and allocate enough >> RAM to run comfortably. Linux & Windows et. al. have their own cache >> of disk blocks. They use very good algorithms for managing this cache. >> Also, they do not make long garbage collection passes. >> >> On Mon, Aug 30, 2010 at 5:48 PM, Amit Nithian wrote= : >> >>> Lance, >>> >>> Thanks for your help. What do you mean by that the OS can keep the inde= x >>> in >>> memory better than Solr? Do you mean that you should use another means = to >>> keep the index in memory (i.e. ramdisk)? Is there a generally accepted >>> heap >>> size/index size that you follow? >>> >>> Thanks >>> Amit >>> >>> On Mon, Aug 30, 2010 at 5:00 PM, Lance Norskog >>> wrote: >>> >>> The price-performance knee for small servers is 32G ram, 2-6 SATA >>>> disks on a raid, 8/16 cores. You can buy these servers and half-fill >>>> them, leaving room for expansion. >>>> >>>> I have not done benchmarks about the max # of processors that can be >>>> kept busy during indexing or querying, and the total numbers: QPS, >>>> response time averages & variability, etc. >>>> >>>> If your index file size is 8G, and your Java heap is 8G, you will do >>>> long garbage collection cycles. The operating system is very good at >>>> keeping your index in memory- better than Solr can. >>>> >>>> Lance >>>> >>>> On Mon, Aug 30, 2010 at 4:52 PM, Amit Nithian >>>> wrote: >>>> > Hi all, >>>> > >>>> > I am curious to know get some opinions on at what point having more = > >>>> CPU >>>> > cores shows diminishing returns in terms of QPS. Our index size is > >>>> about >>>> 8GB >>>> > and we have 16GB of RAM on a quad core 4 x 2.4 GHz AMD Opteron 2216. >>>> > Currently I have the heap to 8GB. >>>> > >>>> > We are looking to get more servers to increase capacity and because = > >>>> the >>>> > warranty is set to expire on our old servers and so I was curious > >>>> before >>>> > asking for a certain spec what others run and at what point does > >>>> having >>>> more >>>> > cores cease to matter? Mainly looking at somewhere between 4-12 core= s >>>> > per >>>> > server. >>>> > >>>> > Thanks! >>>> > Amit >>>> > >>>> >>>> >>>> >>>> -- >>>> Lance Norskog >>>> goksron@gmail.com >>>> >>>> >>> >> >> >> -- >> Lance Norskog >> goksron@gmail.com >> >> > > > -------------------------------------------------------------------------= ------- > > > > ___b___J_T_________f_r_C > Checked by AVG - www.avg.com > Version: 9.0.851 / Virus Database: 271.1.1/3102 - Release Date: 08/30/10 > 14:35:00 > > --001485f872ca6a1868048f164243--