From: Mario Weilguni <mweilguni@sime.com>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Vivek Khera <khera@kcilink.com>
Subject: Re: 8rc2 & BLCKSZ
Date: Thu, 23 Dec 2004 08:00:41 +0100
Message-ID: <200412230800.41210.mweilguni@sime.com> (raw)
In-Reply-To: <20322.1103749490@sss.pgh.pa.us>
References: <FB7893AB-5436-11D9-9A44-000A95DE2550@rilk.com>
<x7llbqf45l.fsf@yertle.int.kciLink.com>
<20322.1103749490@sss.pgh.pa.us>
Am Mittwoch, 22. Dezember 2004 22:04 schrieb Tom Lane:
> Vivek Khera <khera@kcilink.com> writes:
> > One of the suggestions handed to me a long time ago for speeding up PG
> > on FreeBSD was to double the default blocksize in PG. I tried it, but
> > found not a significant enough speed up to make it worth the trouble
> > to remember to patch every version of Pg during the upgrade path (ie,
> > 7.4.0 -> 7.4.2 etc.) Forgetting to do that would be disastrous!
>
> Not really --- the postmaster will refuse to start if the BLCKSZ shown
> in pg_control doesn't match what is compiled in. I concur though that
> there may be no significant performance gain. For some workloads there
> may well be a performance loss from increasing BLCKSZ.
I've several databases of the same version 7.2 with rowsizes from 8k and 32k
with the same workload (a content management system), and the performance of
the 32k variants is slightly better for a few queries, overall responsivness
seems to better with 8k (maybe because the 8k variant has 4x more buffers).
Regards,
Mario Weilguni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mweilguni@sime.com, tgl@sss.pgh.pa.us, khera@kcilink.com
Subject: Re: 8rc2 & BLCKSZ
In-Reply-To: <200412230800.41210.mweilguni@sime.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox