From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Trevor Talbot <quension(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 8.2.3: Server crashes on Windows using Eclipse/Junit |
Date: | 2007-10-26 19:28:35 |
Message-ID: | 47223FE3.8040206@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page wrote:
> Magnus Hagander wrote:
>> VM size in taskmgr should show that I think, and should show a much
>> smaller footprint now..
>
> With patch - 4,492K
> Without patch: 28,224K
>
> Thats with 3 x 100 pgbench connections.
That's nice!
But. That can't be address space usage, it has to be actual memory
usage. Since each thread should chew up 4Mb of address space, and
there's at least two threads in there :-) So looking at the VM column
was obviously not correct.
* looks up some docs*
Right. You need to look at VM size in *process explorer*. VM size in
task manager has nothing to do with VM size, it's the private bytes :-S
And there is no way to see that info from task manager, I think. PE is
your friend.
Anyway. Other than a refresher on those, I'd be interested in two other
important parts:
* How many threads does it reach when you have 300 active backends?
* Is there a handle leak? meaning once your 300 backends have exited,
does the number of handles in the process drop down to the same value it
had before?
(sorry, wish I was in a position to run these tests myself, but I'm not
right now)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-10-26 20:02:22 | Re: 8.2.3: Server crashes on Windows using Eclipse/Junit |
Previous Message | Dave Page | 2007-10-26 19:18:25 | Re: 8.2.3: Server crashes on Windows using Eclipse/Junit |