Re: patch: tsearch - some memory diet

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: patch: tsearch - some memory diet
Дата
Msg-id 4C866B7A.5000006@enterprisedb.com
обсуждение исходный текст
Ответ на Re: patch: tsearch - some memory diet  (Teodor Sigaev <teodor@sigaev.ru>)
Ответы Re: patch: tsearch - some memory diet  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: patch: tsearch - some memory diet  (Teodor Sigaev <teodor@sigaev.ru>)
Re: patch: tsearch - some memory diet  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 07/09/10 19:27, Teodor Sigaev wrote:
>> on 32bit from 27MB (3399 blocks) to 13MB (1564 blocks)
>> on 64bit from 55MB to cca 27MB.
>
> Good results. But, I think, there are more places in ispell to use
> hold_memory():
> - affixes and affix tree
> - regis (REGex for ISpell, regis.c)

A more general solution would be to have a new MemoryContext 
implementation that does the same your patch does. Ie. instead of 
tracking each allocation, just allocate a big chunk, and have palloc() 
return the next n free bytes from it, like a stack. pfree() would 
obviously not work, but wholesale MemoryContextDelete of the whole 
memory context would.

I remember I actually tried this years ago, trying to reduce the 
overhead of parsing IIRC. The parser also does a lot of small 
allocations that are not individually pfree'd. And I think it helped a 
tiny bit, but I didn't pursue it further. But if there's many places 
where it would help, then it might well be worth it.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "David E. Wheeler"
Дата:
Сообщение: Re: function_name.parameter_name
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: patch: tsearch - some memory diet