From owner-freebsd-pkg@FreeBSD.ORG Fri Dec 12 00:08:14 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8ACFEBE9; Fri, 12 Dec 2014 00:08:14 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B526B01; Fri, 12 Dec 2014 00:08:14 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 597F8BDC25; Fri, 12 Dec 2014 01:08:11 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) by prod2.absolight.net (Postfix) with ESMTPA id 39C58BDC24; Fri, 12 Dec 2014 01:08:11 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id 94ADB1EDECC4; Fri, 12 Dec 2014 01:08:08 +0100 (CET) Date: Fri, 12 Dec 2014 01:08:08 +0100 From: Mathieu Arnold To: Dmitry Morozovsky Subject: Re: Frequency of FreeBSD package builds Message-ID: <77E4DBD49647EB45C3CF72B7@atuin.in.mat.cc> In-Reply-To: References: <548428C7.2050800@club-internet.fr> <307D7D309A871FC7AB3405E1@ogg.in.absolight.net> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-pkg@freebsd.org, freebsd-questions@freebsd.org, =?UTF-8?Q?Juan_Ram=C3=B3n_Molina_Menor?= X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 00:08:14 -0000 +--On 12 d=C3=A9cembre 2014 01:56:15 +0300 Dmitry Morozovsky = wrote: | Mat, |=20 | On Mon, 8 Dec 2014, Mathieu Arnold wrote: |=20 |> | Now that the new_xorg and ssp repositories are not being updated any |> | more, what is the reason for the 'beefy' machines to build ports only |> | once a week? Can we expect the frequency of package upgrades to be |> | higher soon? |>=20 |> Right now, it does take 3 to 4 days to build the packages each week, so |> it's a bit hard to make it more often than once a week. We have plans |> for the future, with more building machines, it will be announced when = it |> happens. |=20 | Am I right supposing that each build is a full one? What are the | downsides of incremental builds which should take less than, say, 2 days | (if not deepest beats like gettext updates involved)? No, it is incremental builds, for all port versions of FreeBSD except CURRENT, because ABI change often, and it's safer to just rebuild everything everytime. Right now, there are two boxes, one for amd64 and one for i386, and the build order is the current quarterly branch for 9 and then 10, then head for 10, 9, CURRENT and 8. Also, when there is a security advisory or errata notice and the jails get updated, there is always a full rebuild. This week, the quarterly branches took about 12 hours to build and had each ~6680 ports to build, and for head, the 10 build wanted to build 11744 (out of 24k) took 15h28 to do so, the 9 wants to build 11747 ports, and has been running for 4h50 as of right now. If I look at last week, on the amd64 box, both quarterly only had ~700 ports to build and it took ~1h20, but on head, 10 had 16779 and took 18h26, 9 had 18638 and took 20h33, CURRENT had 24384 (full) and took 27h13, and 8 had 18652 in 19h17. That's about 90 hours of build, which is 3.75 days. I can say off the top of my head that 2*3.75 > 7, so you can't do it twice a week. Also, we *do* need some time to do maintenance, like updating the host, and other stuff. There was a few SA out today, so next week it'll be full build for everybody, it *will* take about 20 hours for each architecture (except CURRENT where it'll be 27h) that'll be a bit more than 5 days. So, long story short, no, we cannot do twice a week *right now* we have more hardware on the way, that will allow us to triple the build power, and when that gets here, we will certainly do package more often, but it's in the future. --=20 Mathieu Arnold