From: Denis Lussier <denisl@enterprisedb.com>
To: Luke Lonergan <llonergan@greenplum.com>
Cc: Milen Kulev <makulev@gmx.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: XFS filessystem for Datawarehousing -2
Date: Thu, 3 Aug 2006 01:36:10 -0400
Message-ID: <5f820f750608022236yd8dd6escce3bb849b91bddb@mail.gmail.com> (raw)
In-Reply-To: <C0F55F94.2B857%llonergan@greenplum.com>
References: <014401c6b5b8$98926a20$0a00a8c0@trivadis.com>
<C0F55F94.2B857%llonergan@greenplum.com>
I was kinda thinking that making the Block Size configurable at InitDB time
would be a nice & simple enhancement for PG 8.3. My own personal rule of
thumb for sizing is 8k for OLTP, 16k for mixed use, & 32k for DWH.
I have no personal experience with XFS, but, I've seen numerous internal
edb-postgres test results that show that of all file systems... OCFS
2.0seems to be quite good for PG update intensive apps (especially on
64 bit
machines).
On 8/1/06, Luke Lonergan <llonergan@greenplum.com> wrote:
>
> Milen,
>
> On 8/1/06 3:19 PM, "Milen Kulev" <makulev@gmx.net> wrote:
>
> > Sorry, forgot to ask:
> > What is the recommended/best PG block size for DWH database? 16k,
> 32k, 64k
> > ?
> > What hsould be the relation between XFS/RAID stripe size and PG block
> size ?
>
> We have found that the page size in PG starts to matter only at very high
> disk performance levels around 1000MB/s. Other posters have talked about
> maintenance tasks improving in performance, but I haven't seen it.
>
> - Luke
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
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: denisl@enterprisedb.com, llonergan@greenplum.com, makulev@gmx.net
Subject: Re: XFS filessystem for Datawarehousing -2
In-Reply-To: <5f820f750608022236yd8dd6escce3bb849b91bddb@mail.gmail.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