Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 4E99E6326E4 for ; Fri, 18 Jun 2010 17:18:42 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 83476-04 for ; Fri, 18 Jun 2010 20:18:33 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id 4047E632277 for ; Fri, 18 Jun 2010 17:18:33 -0300 (ADT) Received: by wyb33 with SMTP id 33so911513wyb.19 for ; Fri, 18 Jun 2010 13:18:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=BZkI7oyC1wmQkww9Fyr4uci7SRDvOfoHIz1aC1VCANs=; b=eR5v6FTC3MQhCTZld9O6Qx4q0V2vyK641Q3tEDUq/P0NPfdZr4li8UXn8nSRz7VqsN baUz9I8zf/XcCQI2ztKc9Tu1OJhF6g+a9TqdhdU84uFEQvVw2A8RFAmjntRicU4HTAZj askGCAmf7xaVGkG6eH91+QRL7sdRQhHJfVD5U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=gV2iiu8lrMgq8Y5EI2iT5+iWRJHb937G8MnvEw7u9+PAeE5s3qq9TBaNgaon2fzdfV /mNnUF5mf0u583VgGMwQcgMkp1/P0rWt3zetTUB28UNrMjPE8wU3WvxJEwyTbrDGg9mK kHOQ9Pajo8F7yAhaautB497XPS9D/rB51hEVQ= Received: by 10.227.133.132 with SMTP id f4mr1454032wbt.189.1276892312314; Fri, 18 Jun 2010 13:18:32 -0700 (PDT) Received: from [0.0.0.0] (5357DA75.cable.casema.nl [83.87.218.117]) by mx.google.com with ESMTPS id y31sm975325wby.22.2010.06.18.13.18.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Jun 2010 13:18:31 -0700 (PDT) Message-ID: <4C1BD4A1.4070406@gmail.com> Date: Fri, 18 Jun 2010 22:18:41 +0200 From: Yeb Havinga User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Kevin Grittner CC: Greg Smith , Matthew Wakeling , Eliot Gable , Robert Haas , pgsql-performance@postgresql.org Subject: Re: B-Heaps References: <4C1BB294.8070806@2ndquadrant.com> <4C1BBB39.10308@gmail.com> <4C1B783602000025000325CE@gw.wicourts.gov> In-Reply-To: <4C1B783602000025000325CE@gw.wicourts.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/342 X-Sequence-Number: 39198 Kevin Grittner wrote: > Yeb Havinga wrote: > > >> concerning gist indexes: >> >> 1) with larger block sizes and hence, larger # entries per gist >> page, results in more generic keys of those pages. This in turn >> results in a greater number of hits, when the index is queried, so >> a larger part of the index is scanned. NB this has nothing to do >> with caching / cache sizes; it holds for every IO model. Tests >> performed by me showed performance improvements of over 200%. >> Since then implementing a speedup has been on my 'want to do >> list'. >> > > As I recall, the better performance in your tests was with *smaller* > GiST pages, right? (The above didn't seem entirely clear on that.) > Yes, making pages smaller made index scanning faster. -- Yeb