Per-session memory footprint (9.0/windows)

From: Hannes Erven <hannes(at)erven(dot)at>
To: pgsql-general(at)postgresql(dot)org
Subject: Per-session memory footprint (9.0/windows)
Date: 2011-03-02 16:07:01
Message-ID: 4D6E6B25.70400@erven.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Folks,

I run a PG (currently 8.4, but will shortly migrate to 9.0) database on
Windows Server 2003 that supports a desktop application which opens a
few long-running sessions per user. This is due to the Hibernate
persistence layer and the "one session per view" pattern that is
recommended for such applications.
These sessions usually load a pile of data once to display to the user,
and then occasionally query updates of this data or even fetch single
rows over a long time (like a few hours).

It seems that each of the server postmaster.exe processes takes up
approx. 5 MB of server memory (the "virtual memory size" column in task
manager), and I guess this truly is the private memory these processes
require. This number is roughly the same for 8.4 and 9.0 .

As there are many, many such server processes running, is there anything
I can do to reduce/optimize the per-session memory footprint?

I'm aware of the sort_mem etc. parameters
(http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server ) but
these seem to only apply to the execution of queries, not to sessions
that mainly "sit around waiting", right?

Thank you for any hints!

-hannes

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Mead 2011-03-02 16:59:43 Re: Per-session memory footprint (9.0/windows)
Previous Message Rayner Julio Rodríguez Pimentel 2011-03-02 15:41:12 I need your help to get opinions about this situation