Skip site navigation (1) Skip section navigation (2)

Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
Date: 2012-03-02 00:23:20
Message-ID: CAGTBQpacHJrTKO9X3qC5_1q2iGz1g7LAc3JvMqMoL5WrZguF3w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, Mar 1, 2012 at 8:08 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> These are extremely low settings on virtually any modern computer. I usually
> look to set shared buffers in numbers of Gb and work_mem at least in tens if
> not hundreds of Mb for any significantly sized database.

For a read-only database, as was discussed, a lower shared_buffers
settings makes sense. And 128M is low enough, I'd guess.

Setting work_mem to hundreds of MB in a 4G system is suicide. Tens
even is dangerous.

In response to

Responses

pgsql-performance by date

Next:From: Peter van HardenbergDate: 2012-03-02 00:28:02
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
Previous:From: Andrew DunstanDate: 2012-03-01 23:08:19
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group