| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: Speed up clean meson builds by ~25% |
| Date: | 2024-04-08 08:00:00 |
| Message-ID: | b564c274-a0b6-a359-e7d5-36bc1f8f53f1@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Michael,
08.04.2024 08:23, Michael Paquier wrote:
> On Fri, Apr 05, 2024 at 06:19:20PM +0200, Jelte Fennema-Nio wrote:
>> Agreed. While not a full solution, I think this patch is still good to
>> address some of the pain: Waiting 10 seconds at the end of my build
>> with only 1 of my 10 cores doing anything.
>>
>> So while this doesn't decrease CPU time spent it does decrease
>> wall-clock time significantly in some cases, with afaict no downsides.
> Well, this is also painful with ./configure. So, even if we are going
> to move away from it at this point, we still need to support it for a
> couple of years. It looks to me that letting the clang folks know
> about the situation is the best way forward.
>
As I wrote in [1], I didn't observe the issue with clang-18, so maybe it
is fixed already.
Perhaps it's worth rechecking...
[1] https://www.postgresql.org/message-id/d2bf3727-bae4-3aee-65f6-caec2c4ebaa8%40gmail.com
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-04-08 08:02:18 | Re: Speed up clean meson builds by ~25% |
| Previous Message | Andrey M. Borodin | 2024-04-08 07:42:08 | Re: Weird test mixup |