From: Steve Eckmann <eckmann@computer.org>
To: Ian Westmacott <ianw@intellivid.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: improving write performance for logging application
Date: Wed, 04 Jan 2006 07:16:33 -0700
Message-ID: <43BBD8C1.9080807@computer.org> (raw)
In-Reply-To: <1136382865.24450.7.camel@spectre.intellivid.com>
References: <43BB0C5C.8020207@computer.org>
<1136382865.24450.7.camel@spectre.intellivid.com>
Ian Westmacott wrote:
>We have a similar application thats doing upwards of 2B inserts
>per day. We have spent a lot of time optimizing this, and found the
>following to be most beneficial:
>
>1) use COPY (BINARY if possible)
>2) don't use triggers or foreign keys
>3) put WAL and tables on different spindles (channels if possible)
>4) put as much as you can in each COPY, and put as many COPYs as
> you can in a single transaction.
>5) watch out for XID wraparound
>6) tune checkpoint* and bgwriter* parameters for your I/O system
>
Thanks, Ian. I will look at how to implement your suggestions.
Regards, Steve
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: eckmann@computer.org, ianw@intellivid.com
Subject: Re: improving write performance for logging application
In-Reply-To: <43BBD8C1.9080807@computer.org>
* 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