X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4491DD7DBE for ; Wed, 5 Oct 2005 00:23:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98262-09 for ; Wed, 5 Oct 2005 03:23:19 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by svr1.postgresql.org (Postfix) with ESMTP id 5AAFDDA0C7 for ; Wed, 5 Oct 2005 00:23:18 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 71so31516wra for ; Tue, 04 Oct 2005 20:23:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=EXNNqjNnrjOZER0lvH+V27qmj3sC7Z1IRrk4+A1JYdE0F1ZF0pS6NxXutrMLeTwHSNB2T5Gx3uLlxx259l2CS0mIG0cLHonqWkyTYtgeamZ0YQ2o2cv9SC8iqmDRdcrRNNcRdJC5dBUtG+/zy5PxuCkyVz8wuaNY0URxXzuNjKw= Received: by 10.54.72.8 with SMTP id u8mr182463wra; Tue, 04 Oct 2005 20:23:17 -0700 (PDT) Received: by 10.54.84.8 with HTTP; Tue, 4 Oct 2005 20:23:17 -0700 (PDT) Message-ID: <33c6269f0510042023t24175e33vf84d9af609a8ccd7@mail.gmail.com> Date: Tue, 4 Oct 2005 23:23:17 -0400 From: Alex Turner Reply-To: Alex Turner To: emil@baymountain.com Subject: Re: Indexes on ramdisk Cc: pgsql-performance@postgresql.org In-Reply-To: <200510042109.01849.emil@baymountain.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14912_24637405.1128482597905" References: <200510042109.01849.emil@baymountain.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.251 required=5 tests=[AWL=-0.069, HTML_10_20=0.295, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200510/66 X-Sequence-Number: 14834 ------=_Part_14912_24637405.1128482597905 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Talk about your IO system a bit. There might be obvious ways to improve. What System/Motherboard are you using? What Controller Cards are you using? What kind of Disks do you have (SATA, SCSI 7.6k 10k 15k) What denominations (9, 18, 36, 72, 143, 80, 160, 200 240Gig)? What kind of RAIDs do you have setup (How many drives what stripe sizes, ho= w many used for what). What levels of RAID are you using (0,1,10,5,50)? With good setup, a dual PCI-X bus motherboard can hit 2GB/sec and thousands of transactions to disk if you have a controller/disks that can keep up. That is typicaly enough for most people without resorting to SSD. Alex Turner NetEconomist On 10/4/05, Emil Briggs wrote: > > > I have an application that has a table that is both read and write > intensive. > Data from iostat indicates that the write speed of the system is the > factor > that is limiting performance. The table has around 20 columns and most of > the > columns are indexed. The data and the indices for the table are > distributed > over several mirrored disk partitions and pg_xlog is on another. I'm > looking > at ways to improve performance and besides the obvious one of getting an > SSD > I thought about putting the indices on a ramdisk. That means that after a > power failure or shutdown I would have to recreate them but that is > acceptable for this application. What I am wondering though is whether or > not > I would see much performance benefit and if there would be any startup > problems after a power down event due to the indices not being present. > Any > insight would be appreciated. > > Emil > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > ------=_Part_14912_24637405.1128482597905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Talk about your IO system a bit.  There might be obvious ways to impro= ve.

What System/Motherboard are you using?
What Controller Cards are you using?
What kind of Disks do you have (SATA, SCSI 7.6k 10k 15k)
What denominations (9, 18, 36, 72, 143, 80, 160, 200 240Gig)?
What kind of RAIDs do you have setup (How many drives what stripe sizes, ho= w many used for what).
What levels of RAID are you using (0,1,10,5,50)?

With good setup, a dual PCI-X bus motherboard can hit 2GB/sec and thousands of transactions  to disk if you have a controller/disks that can keep up.  That is typicaly enough for most people without resorting to SSD.

Alex Turner
NetEconomist

On 10/4/05, Emil Briggs <emil@baymountain.com> wrote:

I have an application that has a table that is both read and write inte= nsive.
Data from iostat indicates that the write speed of the system is = the factor
that is limiting performance. The table has around 20 columns= and most of the
columns are indexed. The data and the indices for the table are distrib= uted
over several mirrored disk partitions and pg_xlog is on another. I'= m looking
at ways to improve performance and besides the obvious one of = getting an SSD
I thought about putting the indices on a ramdisk. That means that after= a
power failure or shutdown I would have to recreate them but that isacceptable for this application. What I am wondering though is whether or= not
I would see much performance benefit and if there would be any startup<= br>problems after a power down event due to the indices not being present. = Any
insight would be appreciated.

Emil

-------------------= --------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

------=_Part_14912_24637405.1128482597905--