pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Maximum Possible Insert Performance?
Date: Sun, 23 Nov 2003 19:48:13 -0800
Message-ID: <bprv1q$1j5o$1@news.hub.org> (raw)

My situation is this. We have a semi-production server where we 
pre-process data and then upload the finished data to our production 
servers. We need the fastest possible write performance. Having the DB 
go corrupt due to power loss/OS crash is acceptable because we can 
always restore from last night and re-run everything that was done since 
then.

I already have fsync off. Short of buying more hardware -- which I will 
probably do anyways once I figure out whether I need more CPU, memory or 
disk -- what else can I do to max out the speed? Operation mix is about 
50% select, 40% insert, 10% update.




view thread (19+ messages)  latest in thread

Message-ID: <bprv1q$1j5o$1@news.hub.org>
Permalink:  ../bprv1q$1j5o$1@news.hub.org/
Also on:    postgresql.org/message-id/bprv1q$1j5o$1@news.hub.org

 · 

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: wyu@talisys.com
  Subject: Re: Maximum Possible Insert Performance?
  In-Reply-To: <bprv1q$1j5o$1@news.hub.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