Re: Horrible PostgreSQL performance with NFS

> > > Did you do those "dd" tests with small block sizes (like 1byte:
> > > bs=1), like somebody on one of those lists suggests, too? Then
> > > we could see, if there is a high latency that ruins
> > > everything...
> > 
> > FYI, PostgreSQL does 8kB I/O by default. This can only be changed
> > by modifying a header file.
> 
> That's definitely small in my book (certainly compared to the 1MB
> block size the first responder suggested), knowing that, you should
> definitely do dd tests with 8k blocks since that's the best
> performance you are likely to get.

PostgreSQL can be configured to use more than 32K blocks, but I recall
65K having problems and shouldn't be used in production.  Tom Lane was
less than amused when he found out I'd added those options to the
ports and issued some strong words suggesting against using anything
but 8K blocks simply because that was the only config that'd seen
years of production use.  YMMV.  -sc

-- 
Sean Chittenden

-----BEGIN PGP SIGNATURE-----

iD8DBQFDz9Tsapga0yeGcOQRAnwjAJ9Q6DVDVGIMKpvauh5RwfdaoIMWtwCgxPJ3
/YO8k5TFeePgp7rPIawg16Q=
=eFD6
-----END PGP SIGNATURE-----