Skip site navigation (1) Skip section navigation (2)

Re: Maximum Possible Insert Performance?

From: Suchandra Thapa <ssthapa(at)netzero(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Maximum Possible Insert Performance?
Date: 2003-11-25 18:59:54
Message-ID: 1069786793.19104.33.camel@hepcat (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Mon, 2003-11-24 at 19:16, Greg Stark wrote:
> William Yu <wyu(at)talisys(dot)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(at)netzero(dot)com>

In response to

pgsql-performance by date

Next:From: Josh BerkusDate: 2003-11-25 19:12:47
Subject: Re: design question: general db performance
Previous:From: Jord TannerDate: 2003-11-25 18:58:28
Subject: Re: design question: general db performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group