From: Jay Manni <JManni@FireEye.com>
To: Craig Ringer <craig@postnewspapers.com.au>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: High Frequency Inserts to Postgres Database vs Writing to a File
Date: Thu, 5 Nov 2009 00:01:36 -0800
Message-ID: <60B0F2124D07B942988329B5B7CA393D01E5B94187@mail2.FireEye.com> (raw)
In-Reply-To: <4AF22671.303@postnewspapers.com.au>
References: <95652FF3B9EF3045AC4AE8FE5AF8671EED65CF6B@mail2.FireEye.com>
<60B0F2124D07B942988329B5B7CA393D01E5B93FF7@mail2.FireEye.com>
<b42b73150911040559w660d1ad2w38a014fbc34e877f@mail.gmail.com>
<4AF22671.303@postnewspapers.com.au>
Thanks to all for the responses. Based on all the recommendations, I am going to try a batched commit approach; along with data purging policies so that the data storage does not grow beyond certain thresholds.
- J
-----Original Message-----
From: Craig Ringer [mailto:craig@postnewspapers.com.au]
Sent: Wednesday, November 04, 2009 5:12 PM
To: Merlin Moncure
Cc: Jay Manni; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] High Frequency Inserts to Postgres Database vs Writing to a File
Merlin Moncure wrote:
> Postgres can handle multiple 1000 insert/sec but your hardware most
> likely can't handle multiple 1000 transaction/sec if fsync is on.
commit_delay or async commit should help a lot there.
http://www.postgresql.org/docs/8.3/static/wal-async-commit.htmlhttp://www.postgresql.org/docs/8.3/static/runtime-config-wal.html
Please do *not* turn fsync off unless you want to lose your data.
> If you are bulk inserting 1000+ records/sec all day long, make sure
> you have provisioned enough storage for this (that's 86M records/day),
plus any index storage, room for dead tuples if you ever issue UPDATEs, etc.
--
Craig Ringer
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
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: JManni@FireEye.com, craig@postnewspapers.com.au, mmoncure@gmail.com
Subject: Re: High Frequency Inserts to Postgres Database vs Writing to a File
In-Reply-To: <60B0F2124D07B942988329B5B7CA393D01E5B94187@mail2.FireEye.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