Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3520417975 for ; Fri, 9 Jan 2015 04:54:16 +0000 (UTC) Received: (qmail 73258 invoked by uid 500); 9 Jan 2015 04:54:13 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 73190 invoked by uid 500); 9 Jan 2015 04:54:13 -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 73157 invoked by uid 99); 9 Jan 2015 04:54:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2015 04:54:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of apache@elyograg.org designates 166.70.79.219 as permitted sender) Received: from [166.70.79.219] (HELO frodo.elyograg.org) (166.70.79.219) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jan 2015 04:54:05 +0000 Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id B14C97617 for ; Thu, 8 Jan 2015 21:53:43 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-transfer-encoding:content-type:content-type:subject :subject:mime-version:user-agent:from:from:date:date:message-id :received:received; s=mail; t=1420779223; bh=BtFuy4Vo2Y9O+AcvOMe Uq5HILjae+hrnxItIFTciBG8=; b=r1bkGET+WyPaiFQ3lERFVzsNrkIYUU+m+zs VMXlLcs3W3tKw+2+idUTA33i9QuLmoGNHvLfsX52R8UPzFaOHylpwDcn4VjMtAAv 0RK37LlAMzxliGzXV4Uo8TGFLOlvIR6S1xupDD8Da68tofRa8lxWj9tmrvXECLSJ 670wnvmE= X-Virus-Scanned: Debian amavisd-new at frodo.elyograg.org Received: from frodo.elyograg.org ([127.0.0.1]) by localhost (frodo.elyograg.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hJf4V1DKYeXX for ; Thu, 8 Jan 2015 21:53:43 -0700 (MST) Received: from [192.168.1.102] (102.int.elyograg.org [192.168.1.102]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: elyograg@elyograg.org) by frodo.elyograg.org (Postfix) with ESMTPSA id 74AD74E75 for ; Thu, 8 Jan 2015 21:53:43 -0700 (MST) Message-ID: <54AF5ED6.6060509@elyograg.org> Date: Thu, 08 Jan 2015 21:53:42 -0700 From: Shawn Heisey User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: solr-user@lucene.apache.org Subject: GC tuning question - can improving GC pauses cause indexing to slow down? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Is it possible that tuning garbage collection to achieve much better pause characteristics might actually *decrease* index performance? Rebuilds that I did while still using a tuned CMS config would take between 5.5 and 6 hours, sometimes going slightly over 6 hours. A rebuild that I did recently with G1 took 6.82 hours. A rebuild that I did yesterday with further tuned G1 settings (which seemed to result in much smaller pauses than the previous G1 settings) took 8.97 hours, and that was on slightly faster hardware than the rebuild that took 6.82 hours. These rebuilds are done with DIH from MySQL. It seems completely counter-intuitive that settings which show better GC pause characteristics would result in indexing performance going down ... so can anyone shed light on this, tell me whether I'm out of my mind? Thanks, Shawn