pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian Hurt <bhurt@janestcapital.com>
To: Guy Rouillier <guyr-ml1@burntmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Making the most of memory?
Date: Wed, 23 Jan 2008 15:50:59 -0500
Message-ID: <4797A8B3.5040605@janestcapital.com> (raw)
In-Reply-To: <47979C15.3040406@burntmail.com>
References: <4796BE84.9030803@centriccrm.com>
	<dcc563d10801222120q78e390dbj2b884eca729c2975@mail.gmail.com>
	<B30794E6-CD2A-43C1-B431-E24B56FBFB1D@concursive.com>
	<dcc563d10801231044p1dba892r9b8bf1269395f068@mail.gmail.com>
	<47979C15.3040406@burntmail.com>

Guy Rouillier wrote:

> Scott Marlowe wrote:
>
>> I assume you're talking about solid state drives?  They have their
>> uses, but for most use cases, having plenty of RAM in your server will
>> be a better way to spend your money.  For certain high throughput,
>> relatively small databases (i.e. transactional work) the SSD can be
>> quite useful.
>
>
> Unless somebody has changes some physics recently, I'm not 
> understanding the recent discussions of SSD in the general press.  
> Flash has a limited number of writes before it becomes unreliable.  On 
> good quality consumer grade, that's about 300,000 writes, while on 
> industrial grade it's about 10 times that.  That's fine for mp3 
> players and cameras; even professional photographers probably won't 
> rewrite the same spot on a flash card that many times in a lifetime.  
> But for database applications, 300,000 writes is trivial. 3 million 
> will go a lot longer, but in non-archival applications, I imagine even 
> that mark won't take but a year or two to surpass.
>
I think the original poster was talking about drives like these:
http://www.texmemsys.com/

Basically, they're not using Flash, they're just big ol' hunks of 
battery-backed RAM.  Not unlike a 10GB battery backed buffer for your 
raid, except there is no raid.

Brian




view thread (21+ messages)  latest in thread

Message-ID: <4797A8B3.5040605@janestcapital.com>
Permalink:  ../4797A8B3.5040605@janestcapital.com/
Also on:    postgresql.org/message-id/4797A8B3.5040605@janestcapital.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: bhurt@janestcapital.com, guyr-ml1@burntmail.com
  Subject: Re: Making the most of memory?
  In-Reply-To: <4797A8B3.5040605@janestcapital.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