pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paesold <mpaesold@gmx.at>
To: Jeffrey W. Baker <jwbaker@acm.org>
Cc: pgsql-general@postgresql.org
Subject: Re: disk performance benchmarks
Date: Wed, 15 Sep 2004 11:39:42 +0200
Message-ID: <003801c49b07$f33b6990$ad01a8c0@zaphod> (raw)
References: <cha71k$3qc@odah37.prod.google.com>
	<x73c1kvjxg.fsf@yertle.int.kciLink.com>
	<1095185498.5792.12.camel@localhost.localdomain>

Jeffrey W. Baker wrote:

> Current issue:
>
> A dual 64-bit Opteron 244 machine with 8GB main memory, two 4-disk RAID5
> arrays (one for database, one for xlogs).  PG's config is extremely
> generous, and in isolated benchmarks it's very fast.

It depends on the controller, but usually I would expect a better
performance if xlogs are just on a two-disk mirror and the rest of the disks
for data (6 splindles instead of 4 then).

I don't think RAID5 is a benefit for xlogs.

Regards,
Michael Paesold

> But, in reality, performance is abyssmal.  There's something about what
> PG does inside commits and checkpoints that sends Linux into a catatonic
> state.  For instance here's a snapshot of vmstat during a parallel heavy
> select/insert load:
...




view thread (16+ messages)  latest in thread

Message-ID: <003801c49b07$f33b6990$ad01a8c0@zaphod>
Permalink:  ../003801c49b07$f33b6990$ad01a8c0@zaphod/
Also on:    postgresql.org/message-id/003801c49b07$f33b6990$ad01a8c0@zaphod

 · 

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: mpaesold@gmx.at, jwbaker@acm.org, pgsql-general@postgresql.org
  Subject: Re: disk performance benchmarks
  In-Reply-To: <003801c49b07$f33b6990$ad01a8c0@zaphod>

* 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