Re: narwhal and PGDLLIMPORT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: narwhal and PGDLLIMPORT
Date: 2014-02-04 22:47:27
Message-ID: 31632.1391554047@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 02/04/2014 03:08 PM, Jeff Janes wrote:
>> Having an AMI would help, but even with an AMI in place, MinGW is
>> still insanely slow. Running "make" on already made PostgreSQL (so
>> there was nothing to actually do) takes 1.5 minutes. And a make after
>> a "make clean" takes half an hour. This is on an actual desktop, not
>> an AWS micro instance. So doing a git bisect is just painful. Is the
>> MSVC build faster?

> Would have to check with the same build options (cassert and debug have
> major timing effects.) I agree it's not lightning fast like "make -j 4"
> on a decent linux box.

I wonder if ccache exists for Mingw. That thing makes a huge difference
in the perceived build speed ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-02-04 22:55:26 Re: Re: Misaligned BufferDescriptors causing major performance problems on AMD
Previous Message Andres Freund 2014-02-04 22:45:30 Re: Wait free LW_SHARED acquisition