| From: | Hannes Erven <hannes(at)erven(dot)at> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | scottm(at)openscg(dot)com |
| Subject: | Re: Per-session memory footprint (9.0/windows) |
| Date: | 2011-03-02 22:24:04 |
| Message-ID: | 4D6EC384.8010401@erven.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 .
>
> Task manager is mis-leading as multiple processes are sharing memory.
> You need process explorer
That's exactly why I did not use the "default" columns of the Task
Manager, but "virtual memory size". I now compared the numbers to the
"private memory" column of Process Explorer, and Process Explorer shows
about 800k even more usage the the Task Manager.
It is still about 5 MB of private memory per "idle" backend process. Is
there anything I can do to optimize?
Thanks again,
-hannes
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-03-02 22:42:42 | Re: Per-session memory footprint (9.0/windows) |
| Previous Message | Ioana Danes | 2011-03-02 21:02:39 | Re: select DISTINCT not ordering the returned rows |