Re: User concurrency thresholding: where do I look?
| От | Simon Riggs |
|---|---|
| Тема | Re: User concurrency thresholding: where do I look? |
| Дата | |
| Msg-id | 1185201556.4284.243.camel@ebony.site обсуждение исходный текст |
| Ответ на | Re: User concurrency thresholding: where do I look? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: User concurrency thresholding: where do I look?
|
| Список | pgsql-performance |
On Mon, 2007-07-23 at 10:11 -0400, Tom Lane wrote: > "Simon Riggs" <simon@2ndquadrant.com> writes: > > EState is about 8300 bytes, > > What? > > (gdb) p sizeof(EState) > $1 = 112 > > This is on a 32-bit machine, but even on 64-bit it wouldn't be more than > double that. > > > Would it be worth a special case in the palloc system to avoid having to > > repeatedly issue external memory allocation calls? > > The appropriate hack would be to change the AllocSetContextCreate > initial-size parameter for the containing context. But I really have > no idea what you're on about. I looked at this last May and my notes say "ExecutorState". I guess that was wrong, but my analysis showed there was a single malloc of 8228 bytes happening once per query during my tests. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
В списке pgsql-performance по дате отправления: