Re: Optimize memory allocation code - Mailing list pgsql-hackers

From Li Japin
Subject Re: Optimize memory allocation code
Date
Msg-id 52DAC3C2-F31A-4C73-B23C-D5C1F99BF38A@hotmail.com
Whole thread Raw
In response to Re: Optimize memory allocation code  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: Optimize memory allocation code  (Merlin Moncure <mmoncure@gmail.com>)
Re: Optimize memory allocation code  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers

> On Sep 26, 2020, at 8:09 AM, Julien Rouhaud <rjuju123@gmail.com> wrote:
> 
> Hi,
> 
> On Sat, Sep 26, 2020 at 12:14 AM Li Japin <japinli@hotmail.com> wrote:
>> 
>> Hi, hackers!
>> 
>> I find the palloc0() is similar to the palloc(), we can use palloc() inside palloc0()
>> to allocate space, thereby I think we can reduce  duplication of code.
> 
> The code is duplicated on purpose.  There's a comment at the beginning
> that mentions it:
> 
>  /* duplicates MemoryContextAllocZero to avoid increased overhead */
> 
> Same for MemoryContextAllocZero() itself.

Thanks! How big is this overhead? Is there any way I can test it?

Best regards!

--
Japin Li

pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: Dynamic gathering the values for seq_page_cost/xxx_cost
Next
From: Merlin Moncure
Date:
Subject: Re: Optimize memory allocation code