From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Improving the memory allocator |
Date: | 2011-04-26 00:22:34 |
Message-ID: | 24250.1303777354@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Apr 25, 2011 at 5:45 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> [ lots of awesome test results ]
> Very interesting work. I think it's interesting that there is so much
> allocation happening inside MessageContext; I barely knew that
> existed, let alone that it was a hotspot for memory allocation.
The reason it shows as a hotspot is that parsing and planning happen in
that context for the simple-Query code path. You'd get different
answers if you were using extended-query protocol, or running prepared
statements, or doing the bulk of your work in plpgsql, etc etc.
It would be interesting if Andres could dig down another level or so in
the call stack to see where the list creations etc are called from, but
I'll bet quite a bit that what we're looking at is mostly parse/plan
activity. (The high showing of bitmapset activity is a dead tipoff for
planner, in particular, since that datatype is hardly used at all
elsewhere.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-04-26 00:22:35 | Speeding up pg_upgrade |
Previous Message | Bruce Momjian | 2011-04-26 00:19:08 | pg_upgrade cleanup |