From: Suchandra Thapa <ssthapa@netzero.com>
To: pgsql-performance@postgresql.org
Subject: Re: Maximum Possible Insert Performance?
Date: 25 Nov 2003 12:59:54 -0600
Message-ID: <1069786793.19104.33.camel@hepcat> (raw)
In-Reply-To: <87brr11c44.fsf@stark.dyndns.tv>
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>
<87brr11c44.fsf@stark.dyndns.tv>
On Mon, 2003-11-24 at 19:16, Greg Stark wrote:
> 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.
I could be wrong, but I was under the impression that most of the newer
flash disks tended to spread writes out over the drive so that hotspots
are minimized.
--
Suchandra Thapa <ssthapa@netzero.com>
Attachments:
signature.asc (application/pgp-signature, 188B) download
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: ssthapa@netzero.com
Subject: Re: Maximum Possible Insert Performance?
In-Reply-To: <1069786793.19104.33.camel@hepcat>
* 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