Re: Force table to be permanently in cache? - Mailing list pgsql-performance

From Andrew Sullivan
Subject Re: Force table to be permanently in cache?
Date
Msg-id 20030829142630.GE19388@libertyrms.info
Whole thread Raw
In response to Force table to be permanently in cache?  (Fabian Kreitner <fabian.kreitner@ainea-ag.de>)
List pgsql-performance
On Fri, Aug 29, 2003 at 02:52:10PM +0200, Fabian Kreitner wrote:
> Hi everyone,
>
> I have a sql request which on first invocation completes in ~12sec but then
> drops to ~3sec on the following runs. The 3 seconds would be acceptable but
> how can I make sure that the data is cached and all times? Is it simply
> enough to set shared_buffers high enough to hold the entire database (and
> have enough ram installed of course)? The OS is linux in this case.

If the table gets hit often enough, then it'll be in your filesystem
cache anyway.  See the many discussions of sizing shared_buffers in
the archives of this list for thoughts on how big that should be.

A

--
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110


pgsql-performance by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: Hardware recommendations to scale to silly load
Next
From: Bill Moran
Date:
Subject: Re: PL/pgSQL functions - text / varchar - havy performance