Date: Tue, 30 May 2023 02:46:53 -0700 From: Mark Millard <marklmi@yahoo.com> To: Nuno Teixeira <eduardo@freebsd.org> Cc: Ronald Klop <ronald-lists@klop.ws>, FreeBSD Mailing List <freebsd-ports@freebsd.org>, freebsd-arm@freebsd.org Subject: Re: Improving www/chromium build time on arm64 Message-ID: <EDC26FF9-0D8D-4412-85F8-21BE157BAF6F@yahoo.com> In-Reply-To: <CAFDf7UK=UQhJt5wi7zk%2BoP%2BCmob5W6Zt-=jkV0rV-kd%2Bm6zMvQ@mail.gmail.com> References: <CAFDf7U%2B1p5HSEmXzSKU62ULgAevGK-g93nBqix2hzafEDs4F-Q@mail.gmail.com> <CAFDf7ULoK-P7h8E2PGz1S3-8Dr8EZLD_o7dWku3eZn7FEXV2Cg@mail.gmail.com> <1623315797.5.1684837400228@mailrelay> <CAFDf7UK=UQhJt5wi7zk%2BoP%2BCmob5W6Zt-=jkV0rV-kd%2Bm6zMvQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 30, 2023, at 01:39, Nuno Teixeira <eduardo@freebsd.org> wrote: > Hello Ronald and all! >=20 > Finally I build it after 57 hours @ 2000MHz !!! So the prior "[88:53:28] Failed ports: www/chromium:build/timeout" was not with the overclocking? Other differences that could contribute to the time difference? MAX_EXECUTION_TIME=3D86400 (the default) only allows for 24 hours before it starts analyzing the log for failure information (while letting the build continue while that scanning is done). > Configs, photos and log at: = https://people.freebsd.org/~eduardo/logs/chromium/ https://people.freebsd.org/~eduardo/logs/chromium/poudriere.conf shows no assignments to MAX_EXECUTION_TIME or NOHANG_TIME or other such (outside comments). In the comments are the default values, not increases. Similarly for PARALLEL_JOBS , PREPARE_PARALLEL_JOBS , ALLOW_MAKE_JOBS , and so on. (It is not clear what the load average behavior/ idle time behavior might have been.) The file does show explicit assignments to: ZPOOL, FREEBSD_HOST , RESOLV_CONF , BASEFS , USE_PORTLINT , USE_TMPFS , DISTFILES_CACHE , and PACKAGE_FETCH_URL . > I'm running it right now and it runs very smooth! >=20 > Next step will be compiling with LTO to check compile time and do some = comparisons on binary size and run performance. >=20 > Should I bother with LTO? Will it add performance? >=20 > Thanks all! >=20 >=20 > Ronald Klop <ronald-lists@klop.ws> escreveu no dia ter=C3=A7a, = 23/05/2023 =C3=A0(s) 11:23: >> =C3=82 =20 >>> Van: Nuno Teixeira <eduardo@freebsd.org> >>> Datum: dinsdag, 23 mei 2023 09:48 >>> Aan: FreeBSD Mailing List <freebsd-ports@freebsd.org>, = freebsd-arm@freebsd.org >>> Onderwerp: Re: Improving www/chromium build time on arm64 >>> (...)=20 >>> =C3=82=20 >>> But I also found that poudriere: >>> [88:53:28] Failed ports: www/chromium:build/timeout >>> =C3=82=20 >>> So I will search how do I increase build time to avoid timeout: >>> --- >>> # This defines the max time (in seconds) that a command may run for = a build >>> # before it is killed for taking too long. Default: 86400 >>> #MAX_EXECUTION_TIME=3D86400 >>> --- >>> =C3=82=20 >>> I suspect it can be the cause of build failure because build >24h. >>> =C3=82 =20 >>> Nuno Teixeira <eduardo@freebsd.org> escreveu no dia ter=C3=83=C2=A7a, = 23/05/2023 =C3=83 (s) 08:31: >>> Hello all,=20 >>> =C3=82=20 >>> I'm running 13-STABLE on rpi4 8 and since firefox{-esr} is = constantly tab crashing and seg faulting I decided to give chromium a = try. >>> chromium pkg isn't available for arm64 and I didn't found error log = at https://pkg-status.freebsd.org/ so I decided to build it on = poudriere. >>> =C3=82=20 >>> It fails to build around 70% but my biggest concern is build time: = 27 hours for 70% compilation! >>> =C3=82=20 >>> Just for comparison: >>> llvm15: 12h >>> rust: 9h >>> firefox: 6h >>> =C3=82=20 >>> rip4 v1.5 8GB @ 2000Hz ~62 Celsius >>> zfs >>> poudriere: >>> USE_TMPFS=3Dno >>> PARALLEL_JOBS=3D1 >>> ALLOW_MAKE_JOBS=3Dyes >>> =C3=82=20 >>> Any hints on how to speed build? ccache? >>> Does cflags "-O -pipe" not present in compilation is related to = build time?=20 >>> =C3=82=20 >>> Full log: >>> = https://people.freebsd.org/~eduardo/logs/chromium/chromium-113.0.5672.126.= log >>> =C3=82=20 >>> Thanks! >>> =C3=82=20 >>> --- >>> <SNIP> >>> In file included from ../../base/check.h:11: >>> ../../base/compiler_specific.h:8:10: fatal error: = 'build/build_config.h' file not found >>> #include "build/build_config.h" >>> ^~~~~~~~~~~~~~~~~~~~~~ >>> 1 error generated. >>> ninja: build stopped: subcommand failed. >>> =3D=3D=3D> Compilation failed unexpectedly. >>> Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the = failure to >>> the maintainer. >>> *** Error code 1 >>>=20 >>> Stop. >>> make: stopped in /usr/ports/www/chromium >>> build of www/chromium | chromium-113.0.5672.126 ended at Tue May 23 = 02:22:56 WEST 2023 >>> build time: 27:15:37 >>> !!! build failure encountered !!! >>> --- >>> -- Nuno Teixeira >>> FreeBSD Committer (ports) >>> =C3=82=20 >>> -- Nuno Teixeira >>> FreeBSD Committer (ports) >>>=20 >>=20 >> Hi, >>=20 >> My poudriere.conf for building ports on rpi4 contains these two = changes: >>=20 >> # This defines the max time (in seconds) that a command may run for a = build >> # before it is killed for taking too long. Default: 86400 >> #MAX_EXECUTION_TIME=3D86400 >> MAX_EXECUTION_TIME=3D172800 >>=20 >> # This defines the time (in seconds) before a command is considered = to >> # be in a runaway state for having no output on stdout. Default: 7200 >> #NOHANG_TIME=3D7200 >> NOHANG_TIME=3D172800 >>=20 >>=20 >> I'm maintaining some mongodb ports which also take a long long time = to build on rpi4. >> But I don't remember which of these settings has the preferred impact = on your situation. >>=20 >> Oh... now I'm reading your log better. It contains this: >> "=3D>> Killing timed out build after 86400 seconds" >>=20 >> And some time later: >> "=3D>> Cleaning up wrkdir >> =3D=3D=3D> Cleaning for chromium-113.0.5672.126" >>=20 >> So the errors about missing files happen because poudriere is = removing files while some processes of the build are still running. >>=20 >> I'm curious how far it gets after you increase MAX_EXECUTION_TIME. >=20 =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?EDC26FF9-0D8D-4412-85F8-21BE157BAF6F>