Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id D89012E00F6 for ; Wed, 23 Jan 2008 17:42:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 95722-02-8 for ; Wed, 23 Jan 2008 17:42:04 -0400 (AST) Received: from mail.emolecules.com (66-226-76-106.dedicated.abac.net [66.226.76.106]) by postgresql.org (Postfix) with ESMTP id B58F02E4575 for ; Wed, 23 Jan 2008 17:06:24 -0400 (AST) Received: (qmail 7107 invoked by uid 2020); 23 Jan 2008 13:06:23 -0800 Received: from wsip-68-224-174-233.sd.sd.cox.net (HELO lisa-james-computer.local) (68.224.174.233) by 192.168.0.4 with SMTP; 23 Jan 2008 13:06:22 -0800 Message-ID: <4797AC4E.6040007@emolecules.com> Date: Wed, 23 Jan 2008 13:06:22 -0800 From: Craig James User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Guy Rouillier , pgsql-performance@postgresql.org Subject: Re: Making the most of memory? References: <4796BE84.9030803@centriccrm.com> <47979C15.3040406@burntmail.com> In-Reply-To: <47979C15.3040406@burntmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/205 X-Sequence-Number: 28444 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. One trick they use is to remap the physical Flash RAM to different logical addresses. Typical apps update a small percentage of the data frequently, and the rest of the data rarely or never. By shuffling the physical Flash RAM around, the media lasts a lot longer than a simple analysis might indicate. Craig