Re: narwhal and PGDLLIMPORT

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 20:53:46
Message-ID: 52F1535A.5090300@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 02/04/2014 03:08 PM, Jeff Janes wrote:
>
>
> Do you know about what it would cost? Could official community funds
> be used for it (it seems like something that is cheap, but which you
> wouldn't want to be forgotten about some month.)
>
> 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.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2014-02-04 21:23:19 Re: GIN improvements part2: fast scan
Previous Message Christian Kruse 2014-02-04 20:30:08 Re: Wait free LW_SHARED acquisition