From: Chris Travers <chris@travelamericas.com>
To: Akshay Mathur <akshay.mathur@airtightnetworks.net>
Cc: Ron <rjpeace@earthlink.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Massive performance issues
Date: Fri, 02 Sep 2005 11:00:46 -0700
Message-ID: <4318934E.7070404@travelamericas.com> (raw)
In-Reply-To: <002901c5afa0$0dcddab0$8301a8c0@pune.wibhu.com>
References: <002901c5afa0$0dcddab0$8301a8c0@pune.wibhu.com>
Akshay Mathur wrote:
>Ron,
>
>Can you give me some pointers to make the tables RAM resident. If one
>does so, is the program accessing the data need to change. Does pgsql
>take care to write the data to disk?
>
>
>
PostgreSQL tried to intelligently cache information and then will also
use the OS disk cache as a secondary cache. So a sufficiently small and
frequently accessed table will be resident in RAM.
The simplest way to affect this calculus is to put more RAM in the
machine. There are hacks I can think of to create RAM caches of
specific tables, but I don't want to take responsibility for anyone
trying these and running into trouble.
Best Wishes,
Chris Travers
Metatron Technology Consulting
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: chris@travelamericas.com, akshay.mathur@airtightnetworks.net, rjpeace@earthlink.net
Subject: Re: Massive performance issues
In-Reply-To: <4318934E.7070404@travelamericas.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