Re: tsearch profiling - czech environment - take 55MB - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tsearch profiling - czech environment - take 55MB
Date
Msg-id 22222.1268327922@sss.pgh.pa.us
Whole thread Raw
In response to Re: tsearch profiling - czech environment - take 55MB  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: tsearch profiling - czech environment - take 55MB
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> The problem is in very large small allocations - there are 853215 nodes.
> I replaced palloc0 inside mkSPnode by balloc

This goes back to the idea we've discussed from time to time of having a
variant memory context type in which pfree() is a no-op and we dispense
with all the per-chunk overhead.  I guess that if there really isn't any
overhead there then pfree/repalloc would actually crash :-( but for the
particular case of dictionaries that would probably be OK because
there's so little code that touches them.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: tsearch profiling - czech environment - take 55MB
Next
From: Pavel Stehule
Date:
Subject: Re: tsearch profiling - czech environment - take 55MB