pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Luke Lonergan <llonergan@greenplum.com>
To: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Marc Mamin <M.Mamin@intershop.de>
Subject: Re: Postgres configuration for 64 CPUs, 128 GB RAM...
Date: Sun, 22 Jul 2007 09:43:47 -0700
Message-ID: <C2C8D753.39643%llonergan@greenplum.com> (raw)
In-Reply-To: <200707201626.08281.josh@agliodbs.com>

Josh,

On 7/20/07 4:26 PM, "Josh Berkus" <josh@agliodbs.com> wrote:

> There are some specific tuning parameters you need for ZFS or performance
> is going to suck.
> 
> http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide
> (scroll down to "PostgreSQL")
> http://www.sun.com/servers/coolthreads/tnb/applications_postgresql.jsp
> http://bugs.opensolaris.org/view_bug.do?bug_id=6437054
> 
> You also don't say anything about what kind of workload you're running.


I think we're assuming that the workload is OLTP when putting these tuning
guidelines forward.  Note that the ZFS tuning guidance referred to in this
bug article recommend "turning vdev prefetching off" for "random I/O
(databases)".  This is exactly the opposite of what we should do for OLAP
workloads.

Also, the lore that setting recordsize on ZFS is mandatory for good database
performance is similarly not appropriate for OLAP work.

If the workload is OLAP / Data Warehousing, I'd suggest ignoring all of the
tuning information from Sun that refers generically to "database".  The
untuned ZFS performance should be far better in those cases.  Specifically,
these three should be ignored:
- (ignore this) limit ARC memory use
- (ignore this) set recordsize to 8K
- (ignore this) turn off vdev prefetch

- Luke





view thread (15+ messages)  latest in thread

Message-ID: <C2C8D753.39643%llonergan@greenplum.com>
Permalink:  ../C2C8D753.39643%25llonergan@greenplum.com/
Also on:    postgresql.org/message-id/C2C8D753.39643%llonergan@greenplum.com

 · 

reply

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: llonergan@greenplum.com, josh@agliodbs.com, M.Mamin@intershop.de
  Subject: Re: Postgres configuration for 64 CPUs, 128 GB RAM...
  In-Reply-To: <C2C8D753.39643%llonergan@greenplum.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