From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Matthew <matthew@flymine.org>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: David Brain <dbrain@bandwidth.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 1 or 2 servers for large DB scenario.
Date: Sun, 27 Jan 2008 10:47:30 +0000
Message-ID: <479C6142.9060502@enterprisedb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801251657530.4642@aragorn.flymine.org>
References: <A97726DE-B9AA-470A-A111-32DB145CAD4A@bandwidth.com>
<Pine.GSO.4.64.0801251144100.13300@westnet.com>
<Pine.LNX.4.64.0801251657530.4642@aragorn.flymine.org>
Matthew wrote:
> On Fri, 25 Jan 2008, Greg Smith wrote:
>> If you're seeing <100TPS you should consider if it's because you're
>> limited by how fast WAL commits can make it to disk. If you really
>> want good insert performance, there is no substitute for getting a
>> disk controller with a good battery-backed cache to work around that.
>> You could just put the WAL xlog directory on a RAID-1 pair of disks to
>> accelerate that, you don't have to move the whole database to a new
>> controller.
>
> Hey, you *just* beat me to it.
>
> Yes, that's quite right. My suggestion was to move the whole thing, but
> Greg is correct - you only need to put the WAL on a cached disc system.
> That'd be quite a bit cheaper, I'd imagine.
>
> Another case of that small SSD drive being useful, I think.
PostgreSQL 8.3 will have "asynchronous commits" feature, which should
eliminate that bottleneck without new hardware, if you can accept the
loss of last few transaction commits in case of sudden power loss:
http://www.postgresql.org/docs/8.3/static/wal-async-commit.html
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
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: heikki@enterprisedb.com, matthew@flymine.org, gsmith@gregsmith.com, dbrain@bandwidth.com
Subject: Re: 1 or 2 servers for large DB scenario.
In-Reply-To: <479C6142.9060502@enterprisedb.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