From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arne Fitzenreiter To: development@lists.ipfire.org Subject: Re: Improving build performance (on slow storage) Date: Wed, 18 Sep 2019 16:31:03 +0200 Message-ID: <8bb6e787a1ae79ef0c89b7f0fa0b84eb@ipfire.org> In-Reply-To: <4C347766-F66C-4943-A3D9-D249652D728B@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2096298652269890532==" List-Id: --===============2096298652269890532== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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 >> 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 >> >> --===============2096298652269890532==--