pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Joshua D. Drake <jd@commandprompt.com>
To: Christiaan Willemsen <cwillemsen@technocon.com>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to setup disk spindles for best performance
Date: Wed, 20 Aug 2008 22:50:38 -0700
Message-ID: <48AD022E.7090400@commandprompt.com> (raw)
In-Reply-To: <331B8FD1-7460-4B97-BD2C-03D8381E1C4D@technocon.com>
References: <972BDF1A-B4ED-46EC-B416-0CDF15A0439A@technocon.com>
	<b42b73150808201849t3577d65eq76e7484d8519af51@mail.gmail.com>
	<331B8FD1-7460-4B97-BD2C-03D8381E1C4D@technocon.com>

Christiaan Willemsen wrote:
> So, what you are basically saying, is that a single mirror is in general 
> more than enough to facilitate the transaction log.

http://www.commandprompt.com/blogs/joshua_drake/2008/04/is_that_performance_i_smell_ext2_vs_ext3_on_...
http://wiki.postgresql.org/wiki/HP_ProLiant_DL380_G5_Tuning_Guide

And to answer your question, yes. Transaction logs are written 
sequentially. You do not need a journaled file system and raid 1 is 
plenty for most if not all work loads.

Sincerely,

Joshua D. Drake

view thread (11+ messages)  latest in thread

Message-ID: <48AD022E.7090400@commandprompt.com>
Permalink:  ../48AD022E.7090400@commandprompt.com/
Also on:    postgresql.org/message-id/48AD022E.7090400@commandprompt.com

copy link · copy postgr.es

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: jd@commandprompt.com, cwillemsen@technocon.com, mmoncure@gmail.com
  Subject: Re: How to setup disk spindles for best performance
  In-Reply-To: <48AD022E.7090400@commandprompt.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