From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Simon Waters <simonw(at)zynet(dot)net> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Drupal and PostgreSQL - performance issues? |
Date: | 2008-10-13 21:21:27 |
Message-ID: | Pine.GSO.4.64.0810131710090.26116@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On Mon, 13 Oct 2008, Simon Waters wrote:
> One of our servers is fairly pressed for memory (some of the time). Is there
> any way to measure the amount of churn in the shared_buffers, as a way of
> demonstrating that more is needed (or at this moment more would help)?
If you wander to http://www.westnet.com/~gsmith/content/postgresql/ my
"Inside the PostgreSQL Buffer Cache" presentation goes over this topic in
extreme detail.
> Can I ask Postgres to tell me, or estimate, how much memory this table
> would occupy if fully cached in memory?
http://wiki.postgresql.org/wiki/Disk_Usage gives an example showing all
the biggest tables/indexes in your data, and links to an article giving
examples of how to find the size of all sorts of things. One of the
queries in my presentation even shows you what % of each table is actually
being cached by the dedicated database memory.
You also need to consider the OS buffer cache to get the full picture,
which is a bit more complicated;
http://www.kennygorman.com/wordpress/?p=250 gives an example there you
might be able to use.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Bennett | 2008-10-14 00:02:04 | Re: Chart of Accounts |
Previous Message | Artacus | 2008-10-13 20:09:53 | Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2008-10-13 21:37:53 | Re: "Mysterious" issues with newly installed 8.3 |
Previous Message | Carlos Moreno | 2008-10-13 19:56:58 | Re: "Mysterious" issues with newly installed 8.3 |