Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
Cc: "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>, ohp(at)pyrenet(dot)fr
Subject: Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before
Date: 2008-04-20 16:02:13
Message-ID: 21342.1208707333@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> writes:
> While working on our network problems to send the full build result to
> the buildfarm server, I just saw that a full buildfarm run with
> -DCLOBBER_CACHE_ALWAYS option takes nearly 2 hours more than before
> (from ~ 5h40 to 7h30).

It's probably due to the RANDOMIZE_ALLOCATED_MEMORY overhead added here:
> pgsql/src/backend/utils/mmgr/aset.c 1.77

Right now that's on by default in assert-enabled builds. I'm not
sure if we want to leave it like that for long ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Smet 2008-04-20 16:32:11 Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before
Previous Message ohp 2008-04-20 15:49:31 Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before