Re: Block size: 8K or 16K? - Mailing list pgsql-hackers

From Neil Conway
Subject Re: Block size: 8K or 16K?
Date
Msg-id 20020425112114.70ad6cf2.nconway@klamath.dyndns.org
Whole thread Raw
In response to Block size: 8K or 16K?  (mlw <markw@mohawksoft.com>)
List pgsql-hackers
On Thu, 25 Apr 2002 09:04:07 -0400
"mlw" <markw@mohawksoft.com> wrote:
> I am going to compare a 16KB PostgreSQL system to an 8KB system. I am working
> on the assumption that 16K takes about as long to read as 8K, and That the CPU
> overhead of working with a 16K block is not too significant. 
> 
> I know with toast, block size is no longer an issue, but 8K is not a lot these
> days, and it seems like a lot of syscall and block management overhead could be
> reduced by doubling it. Any comments?

It's something I was planning to investigate, FWIW. I'd be interested to see
the results...

> The test system is a dual 850MHZ PIII, 1G memory, RedHat 7.2, 2 IBM SCSI 18G
> hard disks, intel motherboard with onboard adaptec SCSI ULVD.
> 
> Besides pgbench, anyone have any tests that they would like to try?

Perhaps OSDB? http://osdb.sf.net

Cheers,

Neil

-- 
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE
Next
From: Bruce Momjian
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE