Date: Tue, 11 Jul 2023 21:14:50 -0700 From: Mark Millard <marklmi@yahoo.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: "Hurling, Rainer" <rhurlin@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: Problem with the package builds Message-ID: <3670BA04-D165-44C3-B5DF-5B5AFD4CFD30@yahoo.com> In-Reply-To: <CAN6yY1uhOTMKkfQZ09Esz4VW-jZ-CNuet_CAKTQ4rTO-pnL2ag@mail.gmail.com> References: <2DCC0132-0307-4A73-A473-B749ABF87367.ref@yahoo.com> <2DCC0132-0307-4A73-A473-B749ABF87367@yahoo.com> <1aaeafcc-9812-64bd-a369-bae7b9fc0e5f@gwdg.de> <422DBC3B-D85F-4AFB-ABDE-842A08482EC8@yahoo.com> <58250d08-ce0a-c1ac-ed15-7d55d517218e@gwdg.de> <2ea168aa-3e0e-ee31-d4a3-82b4ce46b330@gwdg.de> <CAN6yY1sqtLCbqW4%2BxtXfduN7WPPQBnd=FbiknnvDFtGMisveaw@mail.gmail.com> <78c1497b-1ec7-08b6-a407-d671e3c4f9dd@gwdg.de> <ED4C0309-19BB-496D-AA48-462A3303412F@yahoo.com> <CAN6yY1sMceeGHOZHECUHTQKa2UXoXt9x5fdm7A5-b-uyaxCzWQ@mail.gmail.com> <44201182-73C9-46BC-A846-7DC765F5B81F@yahoo.com> <CAN6yY1uhOTMKkfQZ09Esz4VW-jZ-CNuet_CAKTQ4rTO-pnL2ag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 11, 2023, at 21:05, Kevin Oberman <rkoberman@gmail.com> wrote: > On Tue, Jul 11, 2023 at 1:10=E2=80=AFPM Mark Millard = <marklmi@yahoo.com> wrote: > On Jul 11, 2023, at 12:57, Kevin Oberman <rkoberman@gmail.com> wrote: >=20 > > On Mon, Jul 10, 2023 at 9:42=E2=80=AFPM Mark Millard = <marklmi@yahoo.com> wrote: > > On Jul 10, 2023, at 21:27, Rainer Hurling <rhurlin@gwdg.de> wrote: > >=20 > > > As I understand it, the ports-mgmt/pkg of the system running = Poudriere must be updated beforehand? > > >=20 > > > At least on my side, this seems to work as expected :) > > >=20 > >=20 > > poudriere builds pkg updates first (if needed) and then uses the pkg = it > > built for building the later ports into packages. > >=20 > > But, after the restarts of main-* builds, the FreeBSD build servers = are > > still showing examples were, after an 1hr, some builds are still in > > build-depends. Also there was an example I saw were after 1.5 hr it = was > > still in run-depends. > >=20 > > It may be that things are improved but not fully fixed relative to > > some performance issues. > >=20 > > =3D=3D=3D > > Mark Millard > > marklmi at yahoo.com > > A new build started this morning at 1:06 UTC and, with pkg-1.20.2, = it's better, but not much. It's running at 21 packages/hour, a 100% = improvement on the last attempt which appears to have been killed last = night. The logs indicate the installation of dependencies, but I don't = see any sign of caching. It's a re-install every time. (I may not = understand how poudriere does things, but I am pretty sure that caching = is done.) >=20 > Just about "caching" relative to "poudriere bulk" builds . . . >=20 > Nope. At the end of a builder run of a port build the context is = destroyed. > At the start of the builder building its next port the context is = recreated > from scratch. The only ports installed are exactly the declared = dependencies, > no more, no less, for the new port to be built. >=20 > Caching installed state would imply access to ports from prior build > activity that do not apply: It would make the build environment = polluted with > irrelevant history. poudriere's purpose is to have a "clean-room" = context for > each port build. Thus its construction of such a context for each port = build. >=20 > Caching vs. not is not the source of the large increase in how long = things > take to build. >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > OK. I knew it started in a clean jail. I just thought that it might = use some caching technique to speed repeated installs of a single = port... not that I have any idea of how this might be done. >=20 > I think I'll monitor the speed of installs. I iish build logs included = timestamps FYI: Freshports now shows a pkg 1.20.3 described with: pkg*: new regression fixes release Changes: - speed up pkg add again, and greatly reduce its memory footprint - more compatibility with libfetch (SSL_* variables) - fixed FETCH_TIMEOUT adaptation to libcurl Looks to have been committed about 16 hr ago. Last I looked the official package builders had not been stopped and restarted with a newer ports tree yet. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3670BA04-D165-44C3-B5DF-5B5AFD4CFD30>