From: Alan Stange <stange@rentec.com>
To: blblack@gmail.com
Cc: PFC <lists@boutiquenumerique.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance considerations for very heavy INSERT traffic
Date: Mon, 12 Sep 2005 20:38:34 -0400
Message-ID: <43261F8A.1060506@rentec.com> (raw)
In-Reply-To: <84621a60509121502603bd56c@mail.gmail.com>
References: <84621a6050912140464c380c3@mail.gmail.com>
<op.sw0dqyiwth1vuj@localhost>
<84621a60509121502603bd56c@mail.gmail.com>
Brandon Black wrote:
>
>
> On 9/12/05, *PFC* <lists@boutiquenumerique.com
> <mailto:lists@boutiquenumerique.com>> wrote:
>
>
>
> - benchmarking something else than ext3
> (xfs ? reiser3 ?)
>
>
> We've had bad experiences under extreme and/or strange workloads with
> XFS here in general, although this is the first major postgresql
> project - the rest were with other applications writing to XFS. Bad
> experiences like XFS filesystems "detecting internal inconsistencies"
> at runtime and unmounting themselves from within the kernel module
> (much to the dismay of applications with open files on the
> filesystem), on machines with validated good hardware. It has made me
> leary of using anything other than ext3 for fear of stability
> problems. Reiser3 might be worth taking a look at though.
Just one tidbit. We tried XFS on a very active system similar to what
you describe. Dual opterons, 8GB memory, fiber channel drives, 2.6
kernel, etc. And the reliability was awful. We spent a lot of time
making changes one at a time to try and isolate the cause; when we
switched out from XFS to ReiserFS our stability problems went away.
It may be the case that the XFS problems have all been corrected in
newer kernels, but I'm not going to put too much effort into trying that
again.
I recently built a postgres with 32KB block sizes and have been doing
some testing. For our particular workloads it has been a win.
-- Alan
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: stange@rentec.com, blblack@gmail.com, lists@boutiquenumerique.com
Subject: Re: Performance considerations for very heavy INSERT traffic
In-Reply-To: <43261F8A.1060506@rentec.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