pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pierre Frédéric Caillaud <lists@peufeu.com>
To: fkater@googlemail.com <fkater@googlemail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Inserting 8MB bytea: just 25% of disk perf used?
Date: Fri, 15 Jan 2010 00:19:56 +0100
Message-ID: <op.u6jpripycke6l8@soyouz> (raw)
In-Reply-To: <20100114212807.GF2384@comppasch2>
References: <20100114142903.GB2973@comppasch2>
	<op.u6i5s9eicke6l8@soyouz>
	<20100114212807.GF2384@comppasch2>

On Thu, 14 Jan 2010 22:28:07 +0100, fkater@googlemail.com  
<fkater@googlemail.com> wrote:

> Pierre Frédéric Caillaud:
>
>> > 4 Core CPU 3 Ghz, WinXP, 1 TB SATA disk.
>>
>> 	Big CPU and slow disk...
>>
>> 	You should add another disk just for the WAL -- disks are pretty cheap
>> these days.
>> 	Writing the WAL on a second disk is the first thing to do on a
>> configuration like yours, if you are limited by writes.
>> 	It also reduces the fsync lag a lot since the disk is only doing WAL.
>
> Good idea -- where can I set the path to WAL?

	At install, or use a symlink (they exist on windows too !...)

	http://stackoverflow.com/questions/1901405/postgresql-wal-on-windows

	I've no idea of the other needed NTFS tweaks, like if there is a  
noatime/nodiratime ?...





view thread (16+ messages)  latest in thread

Message-ID: <op.u6jpripycke6l8@soyouz>
Permalink:  ../op.u6jpripycke6l8@soyouz/
Also on:    postgresql.org/message-id/op.u6jpripycke6l8@soyouz

 · 

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: lists@peufeu.com, fkater@googlemail.com
  Subject: Re: Inserting 8MB bytea: just 25% of disk perf used?
  In-Reply-To: <op.u6jpripycke6l8@soyouz>

* 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