Re: Mapping a database completly into Memory - Mailing list pgsql-performance

From Franco Bruno Borghesi
Subject Re: Mapping a database completly into Memory
Date
Msg-id 1059401815.749.7.camel@taz.oficina
Whole thread Raw
In response to Re: Mapping a database completly into Memory  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Mapping a database completly into Memory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
wouldn't also increasing shared_buffers to 64 or 128 MB be a good performance improvement? This way, pages belonging to heavily used indexes would be already cached by the database itself.

Please, correct me if I'm wrong.

On Mon, 2003-07-28 at 01:14, Josh Berkus wrote:
Daniel,

> > I just wondered if there is a possibility to map my database running
> > on a linux system completly into memory and to only use disk
> > accesses for writes.
>
> That happens for free, if you have enough RAM.  The kernel will use
> spare RAM to hold copies of every disk block it's ever read.

Also, don't forget to raise your effective_cache_size so that PostgreSQL 
*knows* that you have lots of RAM.
Attachment

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Mapping a database completly into Memory
Next
From: Josh Berkus
Date:
Subject: Re: Mapping a database completly into Memory