Re: Mapping a database completly into Memory

From: Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Daniel Migowski <postgresql(at)Mig-O(dot)de>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Mapping a database completly into Memory
Date: 2003-07-28 14:16:55
Message-ID: 1059401815.749.7.camel@taz.oficina
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Justin Long 2003-07-28 16:18:55 Optimization
Previous Message Josh Berkus 2003-07-28 04:14:11 Re: Mapping a database completly into Memory