pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@myrealbox.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maximum Possible Insert Performance?
Date: Mon, 24 Nov 2003 11:20:36 +0530
Message-ID: <3FC19C2C.4050704@myrealbox.com> (raw)
In-Reply-To: <bprv1q$1j5o$1@news.hub.org>
References: <bprv1q$1j5o$1@news.hub.org>

William Yu wrote:

> 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.

Mount WAL on RAM disk. WAL is most often hit area for heavy updates/inserts. If 
you spped that up, things should be pretty faster.

A non-tried advice though. Given that you can afford a crash, I would say it is 
worth a try..

  Shridhar




view thread (19+ messages)  latest in thread

Message-ID: <3FC19C2C.4050704@myrealbox.com>
Permalink:  ../3FC19C2C.4050704@myrealbox.com/
Also on:    postgresql.org/message-id/3FC19C2C.4050704@myrealbox.com

 · 

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: shridhar_daithankar@myrealbox.com
  Subject: Re: Maximum Possible Insert Performance?
  In-Reply-To: <3FC19C2C.4050704@myrealbox.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