X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id DD151D1C7F2 for ; Mon, 28 Jul 2003 14:14:20 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 92696-09 for ; Mon, 28 Jul 2003 11:13:28 -0300 (ADT) Received: from lucifer.akyasociados.com.ar (unknown [200.69.203.237]) by svr1.postgresql.org (Postfix) with ESMTP id CECA2D1C7F8 for ; Mon, 28 Jul 2003 11:14:17 -0300 (ADT) Received: from taz.oficina (taz.oficina [192.168.1.174]) (authenticated bits=0) by lucifer.akyasociados.com.ar (8.12.9/8.12.9) with ESMTP id h6SEH6so072554; Mon, 28 Jul 2003 11:17:06 -0300 (ART) (envelope-from franco@akyasociados.com.ar) Subject: Re: Mapping a database completly into Memory From: Franco Bruno Borghesi To: Josh Berkus Cc: Daniel Migowski , pgsql-performance@postgresql.org In-Reply-To: <200307272114.11579.josh@agliodbs.com> References: <97842368.20030727104901@artis.uni-oldenburg.de> <9002.1059322732@sss.pgh.pa.us> <200307272114.11579.josh@agliodbs.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-VTGh5l54Wmx+UnmEEkZB" Organization: AK y Asociados S.R.L. Message-Id: <1059401815.749.7.camel@taz.oficina> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 28 Jul 2003 11:16:55 -0300 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/437 X-Sequence-Number: 2730 --=-VTGh5l54Wmx+UnmEEkZB Content-Type: multipart/alternative; boundary="=-eoPw81zciwjNmxSan3/f" --=-eoPw81zciwjNmxSan3/f Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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, >=20 > > > 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. >=20 > Also, don't forget to raise your effective_cache_size so that PostgreSQL= =20 > *knows* that you have lots of RAM. --=-eoPw81zciwjNmxSan3/f Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable wouldn't also increasing shared_buffers to 64 or 128 MB be a good performan= ce 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 runn=
ing
> > 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=20
*knows* that you have lots of RAM.
--=-eoPw81zciwjNmxSan3/f-- --=-VTGh5l54Wmx+UnmEEkZB Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/JTBX21dVnhLsBV0RAnenAJ9B95hov69+OqrhIN2cxy6ncl/b8wCdGwX0 puFd21I4zVEunwszQFtTvOc= =DiiU -----END PGP SIGNATURE----- --=-VTGh5l54Wmx+UnmEEkZB--