Date: Thu, 24 Aug 2023 15:20:50 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: www/chromium will not build on a host w/ 8 CPU and 16G mem [RPi4B 8 GiByte example] Message-ID: <804E6287-71B7-4D2C-A72C-6FA681311139@yahoo.com> References: <804E6287-71B7-4D2C-A72C-6FA681311139.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
bob prohaska <fbsd_at_www.zefox.net> wrote on
Date: Thu, 24 Aug 2023 19:44:17 UTC :
> On Fri, Aug 18, 2023 at 08:05:41AM +0200, Matthias Apitz wrote:
> >=20
> > sysctl vfs.read_max=3D128
> > sysctl vfs.aio.max_buf_aio=3D8192
> > sysctl vfs.aio.max_aio_queue_per_proc=3D65536
> > sysctl vfs.aio.max_aio_per_proc=3D8192
> > sysctl vfs.aio.max_aio_queue=3D65536
> > sysctl vm.pageout_oom_seq=3D120
> > sysctl vm.pfault_oom_attempts=3D-1=20
> >=20
>=20
> Just tried these settings on a Pi4, 8GB. Seemingly no help,
> build of www/chromium failed again, saying only:
>=20
> =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
> No messages on the console at all, no indication of any swap use at =
all.
> If somebody can tell me how to invoke MAKE_JOBS_UNSAFE=3Dyes, either
> locally or globally, I'll give it a try. But, if it's a system problem
> I'd expect at least a peep on the console....
Are you going to post the log file someplace? You may have
missed an earlier message. How long had it run before
stopping? How does that match up with the MAX_EXECUTION_TIME
and NOHANG_TIME and the like that you have poudriere set
up to use ( /usr/local/etc/poudriere.conf ). Something
relevant for the question is what you have for:
# Grep build logs to determine a possible build failure reason. This is
# only shown on the web interface.
# Default: yes
DETERMINE_BUILD_FAILURE_REASON=3Dno
Using DETERMINE_BUILD_FAILURE_REASON leads to large builds
running for a long time after it starts the process of
stopping from a timeout> the grep activity takes a long
time and the build activity is not stopped during the
grep.
vm.pageout_oom_seq=3D120 and vm.pfault_oom_attempts=3D-1 make
sense to me for certain kinds of issues involved in large
builds, presuming sufficient RAM+SWAP for how it is set
up to operate. vm.pageout_oom_seq is associated with
console/log messages. if one runs out of RAM+SWAP,
vm.pfault_oom_attempts=3D-1 tends to lead to deadlock. But
it allows slow I/O to have the time to complete and so
can be useful.
I'm not sure that any vfs.aio.* is actually involved: special
system calls are involved, splitting requests vs. retrieving
the status of completed requests later. Use of aio has to be
explicit in the running software from what I can tell. I've
no information about which software builds might be using aio
during the build activity.
# sysctl -d vfs.aio
vfs.aio: Async IO management
vfs.aio.max_buf_aio: Maximum buf aio requests per process
vfs.aio.max_aio_queue_per_proc: Maximum queued aio requests per process
vfs.aio.max_aio_per_proc: Maximum active aio requests per process
vfs.aio.aiod_lifetime: Maximum lifetime for idle aiod
vfs.aio.num_unmapped_aio: Number of aio requests presently handled by =
unmapped I/O buffers
vfs.aio.num_buf_aio: Number of aio requests presently handled by the buf =
subsystem
vfs.aio.num_queue_count: Number of queued aio requests
vfs.aio.max_aio_queue: Maximum number of aio requests to queue, globally
vfs.aio.target_aio_procs: Preferred number of ready kernel processes for =
async IO
vfs.aio.num_aio_procs: Number of presently active kernel processes for =
async IO
vfs.aio.max_aio_procs: Maximum number of kernel processes to use for =
handling async IO=20
vfs.aio.unsafe_warningcnt: Warnings that will be triggered upon failed =
IO requests on unsafe files
vfs.aio.enable_unsafe: Permit asynchronous IO on all file types, not =
just known-safe types
vfs.read_max may well change the disk access sequences:
# sysctl -d vfs.read_max
vfs.read_max: Cluster read-ahead max block count
That might well help some spinning rust or other types of
I/O.
MAKE_JOBS_UNSAFE=3Dyes is, for example, put in makefiles of
ports that have problems with parallel build activity. It
basically disables having parallel activity in the build
context involved. I've no clue if you use the likes of,
say,
/usr/local/etc/poudriere.d/make.conf
with conditional logic inside such as use of notation
like:
.if ${.CURDIR:M*/www/chromium}
STUFF HERE
.endif
but you could.
=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?804E6287-71B7-4D2C-A72C-6FA681311139>