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: Re: Maximum Possible Insert Performance?
Date: Mon, 24 Nov 2003 09:19:20 -0800
Message-ID: <bpteip$13d$1@news.hub.org> (raw)
In-Reply-To: <3FC19C2C.4050704@myrealbox.com>
References: <bprv1q$1j5o$1@news.hub.org>
	<3FC19C2C.4050704@myrealbox.com>

This is an intriguing thought which leads me to think about a similar 
solution for even a production server and that's a solid state drive for 
just the WAL. What's the max disk space the WAL would ever take up? 
There's quite a few 512MB/1GB/2GB solid state drives available now in 
the ~$200-$500 range and if you never hit those limits...

When my current job batch is done, I'll save a copy of the dir and give 
the WAL on ramdrive a test. And perhaps even buy a Sandisk at the local 
store and run that through the hooper.


Shridhar Daithankar wrote:
> 
> 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.




view thread (19+ messages)  latest in thread

Message-ID: <bpteip$13d$1@news.hub.org>
Permalink:  ../bpteip$13d$1@news.hub.org/
Also on:    postgresql.org/message-id/bpteip$13d$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: <bpteip$13d$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