From: Michael Stone <mstone+postgres@mathom.us>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Performance nightmare with dspam (urgent) (resolved)
Date: Mon, 06 Jun 2005 13:27:40 -0400
Message-ID: <20050606172740.GC19670@mathom.us> (raw)
In-Reply-To: <42A47129.30309@arbash-meinel.com>
References: <200506012019.13218.cshobe@seattleserver.com>
<200506061454.48018.lists@seattleserver.com>
<42A466E7.4080808@arbash-meinel.com>
<20050606151911.GB19670@mathom.us>
<42A47129.30309@arbash-meinel.com>
On Mon, Jun 06, 2005 at 10:52:09AM -0500, John A Meinel wrote:
>pg_xlog benefits from being super fast. Because it has to be fully
>synced before the rest of the data can be committed. Yes they are small,
>but if you can make it fast, you eliminate that overhead. It also
>benefits from having it's own spindle, because you eliminate the seek
>time. (Since it is always appending)
Eliminating the seeks is definately a win.
>Anyway, my point is that pg_xlog isn't necessarily tiny. Many people
>seem to set it as high as 100-200, and each one is 16MB.
It's not the size of the xlog, it's the size of the write. Unless you're
writing out a stripe size of data at once you're only effectively
writing to one disk pair at a time anyway. (Things change if you have a
big NVRAM cache to aggregate the writes, but you'd need a *lot* of
transaction activity to exceed the 50MB/s or so you could get from the
single raid1 pair in that scenario.)
Mike Stone
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: mstone+postgres@mathom.us
Subject: Re: Performance nightmare with dspam (urgent) (resolved)
In-Reply-To: <20050606172740.GC19670@mathom.us>
* 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