From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Improving build performance (on slow storage)
Date: Wed, 18 Sep 2019 16:31:03 +0200 [thread overview]
Message-ID: <8bb6e787a1ae79ef0c89b7f0fa0b84eb@ipfire.org> (raw)
In-Reply-To: <4C347766-F66C-4943-A3D9-D249652D728B@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
If this was the first core136 build it is normal because it has a new
toolchain package and this invalidate the ccache so
all has to rebuild without cache.
Arne
Am 2019-09-17 22:30, schrieb Michael Tremer:
> Hi,
>
> Is that a repeated build?
>
> Do you know which package took extremely long?
>
> The nightly builds seem to be fine at around 4:30 hrs.
>
> -Michael
>
>> On 17 Sep 2019, at 12:18, Matthias Fischer
>> <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi,
>>
>> On 13.06.2019 17:17, Michael Tremer wrote:
>>> Hello,
>>>
>>> I just wanted to post you an update about the build system which we
>>> have recently merged.
>>>
>>> ...
>>
>> I'm bringing this thread up again because beginning with Core 136, I
>> notice a significant deceleration.
>>
>> Last - clean - build from tonight:
>>
>> ...
>> Checking Logfiles for new Files
>> *** Build finished in 12:28:46
>> ...
>>
>> That's a new record. Build time with Core 135 was about 7-8 hours.
>>
>> Is it the same for others?
>>
>> Best,
>> Matthias
>>
>>
next prev parent reply other threads:[~2019-09-18 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 15:17 Michael Tremer
2019-06-15 10:03 ` Matthias Fischer
2019-06-15 13:51 ` Michael Tremer
2019-06-15 14:12 ` Matthias Fischer
2019-09-17 16:18 ` Matthias Fischer
2019-09-17 20:30 ` Michael Tremer
2019-09-18 14:31 ` Arne Fitzenreiter [this message]
2019-09-18 16:42 ` Matthias Fischer
2019-09-18 16:42 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bb6e787a1ae79ef0c89b7f0fa0b84eb@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox