[GENERAL] Per-session memory footprint (9.0/windows)

2011-03-02 Thread Hannes Erven
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

Re: [GENERAL] Per-session memory footprint (9.0/windows)

2011-03-02 Thread Scott Mead
On Wed, Mar 2, 2011 at 11:07 AM, Hannes Erven han...@erven.at wrote: 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

Re: [GENERAL] Per-session memory footprint (9.0/windows)

2011-03-02 Thread Hannes Erven
Scott, 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 .

Re: [GENERAL] Per-session memory footprint (9.0/windows)

2011-03-02 Thread Tom Lane
Hannes Erven han...@erven.at writes: It is still about 5 MB of private memory per idle backend process. Is there anything I can do to optimize? That sounds about the right ballpark for a working backend process with caches loaded up. If that's too much for you, you ought to be using connection