Re: profiling connection overhead
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Date: 2010-11-30T03:35:52Z
Lists: pgsql-hackers
Greg Stark wrote: > On Mon, Nov 29, 2010 at 12:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > The most portable way to do that would be to use calloc insted of malloc, > > and hope that libc is smart enough to provide freshly-mapped space. > > It would be good to look and see whether glibc actually does so, > > of course. ?If not we might end up having to mess with sbrk for > > ourselves, and I'm not sure how pleasantly that interacts with malloc. > > It's *supposed* to interact fine. The only thing I wonder is that I > think malloc intentionally uses mmap for larger allocations but I'm > not clear what the advantages are. Is it because it's a cheaper way to > get zeroed bytes? Or just so that free has a hope of returning the > allocations to the OS? Using mmap() so you can return large allocations to the OS is a neat trick, certainly. I am not sure who implements that. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +