X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5354F52A23 for ; Fri, 29 Jul 2005 13:50:11 -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 87292-06 for ; Fri, 29 Jul 2005 16:50:09 +0000 (GMT) Received: from mail.travelamericas.com (unknown [206.130.134.147]) by svr1.postgresql.org (Postfix) with SMTP id 1CB73529FA for ; Fri, 29 Jul 2005 13:50:08 -0300 (ADT) Received: (qmail 18691 invoked from network); 29 Jul 2005 16:50:07 -0000 Received: from unknown (HELO ?10.0.0.253?) (10.0.0.253) by verkiel.travelamericas.com with SMTP; 29 Jul 2005 16:50:07 -0000 Message-ID: <42EA5E3F.4090909@travelamericas.com> Date: Fri, 29 Jul 2005 09:50:07 -0700 From: Chris Travers User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Lane Cc: pgsql-admin@postgresql.org Subject: Re: Indexes on RAM disk = insanity? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.037 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200507/252 X-Sequence-Number: 18308 Steve Lane wrote: >All: > >We have a postgres 7.4 server where we're trying to achieve some speedups. >Right now, at least superficially, RAM appears to be the bottleneck -- lots >of swaps in and out. > >There is another consultant beside myself in the mix and he asked this >question: can we put the database indexes on a RAM disk? Won't that speed >things up? > > I am quite wary about putting the indexes on a RAM DISK for another reason. You say that RAM is your bottleneck, so putting anything unnecessary in RAM seems like a good way to get less performance rather than more. Additionally you have some overhead in tracking the files, etc. and they will remain in RAM even when they are not used. This leaves the system with less effective RAM for the memory intensive operations. Such a move might make a lot of sense if you had a LOT of RAM but disk I/O was the bottleneck. However, if a lack of RAM is your problem, putting more stuff in RAM doesn't seem very sound to me. Best Wishes, Chris Travers Metatron Technology Consulting