Why does splitting $PGDATA and xlog yield a performance benefit?

From: David Kerr <dmk(at)mr-paradox(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Why does splitting $PGDATA and xlog yield a performance benefit?
Date: 2015-08-25 17:08:48
Message-ID: 20150825170848.GA2656@mr-paradox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Howdy All,

For a very long time I've held the belief that splitting PGDATA and xlog on linux systems fairly universally gives a decent performance benefit for many common workloads.
(i've seen up to 20% personally).

I was under the impression that this had to do with regular fsync()'s from the WAL
interfearing with and over-reaching writing out the filesystem buffers.

Basically, I think i was conflating fsync() with sync().

So if it's not that, then that just leaves bandwith (ignoring all of the other best practice reasons for reliablity, etc.). So, in theory if you're not swamping your disk I/O then you won't really benefit from relocating your XLOGs.

However, I know from experience that's not entirely true, (although it's not always easy to measure all aspects of your I/O bandwith).

Am I missing something?

Thanks

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andomar 2015-08-25 17:16:37 Re: Why does splitting $PGDATA and xlog yield a performance benefit?
Previous Message Melvin Davidson 2015-08-25 16:54:13 Re: PostgreSQL Developer Best Practices