Re: Mapping a database completly into Memory

From: Vivek Khera <khera(at)kcilink(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Mapping a database completly into Memory
Date: 2003-07-31 14:15:04
Message-ID: 16169.9320.444739.336507@yertle.int.kciLink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>>>> "BM" == Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

BM> I think it all depends on your working set. Having shared memory be
BM> smaller than you working set causes pages to have to be copied in from
BM> the kernel buffers (not a huge problem, but a small penalty), while
BM> having shared memory larger than the working set causes overhead of
BM> searching through all those buffers.

i.e., It is a black art, and no single piece of advice can be taken in
isolation ;-(

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message cafweb 2003-07-31 14:43:00 Re: postgresql.conf
Previous Message Rod Taylor 2003-07-31 12:11:58 Re: Possible problem with DOMAIN evaluation?