pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Maximum Possible Insert Performance?
Date: 24 Nov 2003 20:16:27 -0500
Message-ID: <87brr11c44.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <bptib8$d5s$1@news.hub.org>
References: <bprv1q$1j5o$1@news.hub.org>
	<200311240925.58070.josh@agliodbs.com>
	<bptg3i$64u$1@news.hub.org>
	<200311241004.37969.josh@agliodbs.com>
	<bptib8$d5s$1@news.hub.org>

William Yu <wyu@talisys.com> writes:

> > You're right, though, mirroring a solid state drive is pretty pointless; if
> > power fails, both mirrors are dead.
> 
> Actually no. Solid state memory is non-volatile. They retain data even without
> power.

Note that flash ram only has a finite number of write cycles before it fails.

On the other hand that might not be so bad for WAL which writes sequentially,
you can easily calculate how close you are to the maximum. For things like
heap storage or swap it's awful as you can get hot spots that get written to
thousands of times before the rest of the space is used.

-- 
greg




view thread (19+ messages)  latest in thread

Message-ID: <87brr11c44.fsf@stark.dyndns.tv>
Permalink:  ../87brr11c44.fsf@stark.dyndns.tv/
Also on:    postgresql.org/message-id/87brr11c44.fsf@stark.dyndns.tv

 · 

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: gsstark@mit.edu, wyu@talisys.com
  Subject: Re: Maximum Possible Insert Performance?
  In-Reply-To: <87brr11c44.fsf@stark.dyndns.tv>

* 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