From nobody Sun Sep 14 16:35:27 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cPv0y4Gb6z686gP for ; Sun, 14 Sep 2025 16:35:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cPv0y25pzz3Sy3 for ; Sun, 14 Sep 2025 16:35:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102a.google.com with SMTP id 98e67ed59e1d1-329a41dc2ebso2937276a91.3 for ; Sun, 14 Sep 2025 09:35:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1757867740; x=1758472540; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=a79yG1HhlbRodpRUzEn1vrYbEVjh087NlOniySvRJfU=; b=aCCb7QtzOMl4/xkUsueflWbWheWYT3uh18XunoGZEP9fNZ//9DZ+TA2HkkaKVexZ32 FtffRsXqHxjaHW/k/DcHY0mABomMvk0XrR3z7KFn0srpwcbEHo6CRTLUvvcWj9XH6gfG bQ0dfaRG6wJdqAKFbkgn1Ry/pO6HvtohHqgWH+R++G4j+SfDMK7HsnxzZXyhfmtPSzEl gg43BcWdcFqjVTnMlvNQOBwpo1DusiYHO0Wn7uRl800xLo54q+EzJs0f9FBqLzU/6XTB xaPWuE4PehfSKAkMxE2bouMaMB42e5xPXgpnqhNwDX8YdimfFpWs50CEC+jkxhrvHCVk Ymxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757867740; x=1758472540; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=a79yG1HhlbRodpRUzEn1vrYbEVjh087NlOniySvRJfU=; b=f5p9A+hw3dHhFhnPfavTGb9HDoe2Ci/ZhlGdf04OFRULNGXLoY+zDW33luqhI1Du24 aGGMCVqZICTSGywAbLwMWWeMAsgaezAnoc3X6+aOso7EQhhWv7uEFgQYPz1+b8GaK1kW dlg+S2pt4T9eS/I4guWKhmsQpDSNMqytZe41APStkK3t1x+xc7VXFkiULD49jdxf1Zp6 cyI4f2tRWbUABi1rqzlROr9ducjhNGTiHSdH3bqFWlyJEx5Wx1PWU48P/fmVRmPkn0ML xg8PTcBC1NAOzVz0VazqNXIB7dn+TrWpH1i6Rzx7xEcJRbOBp7OCegq5ziCB+3golbWM sy4w== X-Forwarded-Encrypted: i=1; AJvYcCXuxCHwUQhOzGnmqKB53L8nUhvTcAp0kF9IBVB9nlIR/+P0FJZzH98DAODNwUxerPzsNaUgHcl7u4E+AlyJN8o=@freebsd.org X-Gm-Message-State: AOJu0YyosMAGNVW09CWR8bx7a9s/8jIjhSCCei1cHAhRuNj+C7Ry8ecb hPkN37G5Crae347SUL13QNy3iH7tIOYHIbKeRJHw5FPF+P9N/ztSLtCnBNafoi1w1KXh0xMh50+ smEtn5y8QMjcBtzK5NRqehk0xxNi+F+Z4nLaBqe9FQw== X-Gm-Gg: ASbGncsyWHSy+4O82XSsc9qIu9YwwG02o5lNMUaNFiDULnLEvHYVrxJWjT4eF8AL0Ho O+44YHg8M3K0aqPjuKwUIvR7sTxKKNKSPSG0j63QGxJ/8qp144t69tB/7tISz65aRzrX3HLihhb XwLH4trPcGtivkUdfntJCgBkFIwBGRNf5ootxsiiZMmU+sYVhJXEQRrGnDd74a7Tp3WqKg7dNx+ +cftODYArp03RykWfTz/rN8R05qgxd9pdZdYqHL9shV1jGQAg== X-Google-Smtp-Source: AGHT+IFT02AvrdIUIAqcUWGB8T3lBKb0WDk3HuvKo/GL9/1nfarvEswxkGRrh4/JTCYsEkYXSg1gVIwEVdVXMbGjAKY= X-Received: by 2002:a17:90b:2d06:b0:32e:5646:d43f with SMTP id 98e67ed59e1d1-32e5646d936mr984864a91.19.1757867740089; Sun, 14 Sep 2025 09:35:40 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 14 Sep 2025 10:35:27 -0600 X-Gm-Features: Ac12FXwco9DjPqhlS4r8tpJBCuMvf7C8kHo3ZSZi8lglUaXyNzDb2Oq8mwNny8Q Message-ID: Subject: Re: Git and buildworld running at the same time To: bob prohaska Cc: Brad Davis , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000035dd9b063ec57a82" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cPv0y25pzz3Sy3 --00000000000035dd9b063ec57a82 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Sep 14, 2025 at 10:25=E2=80=AFAM bob prohaska = wrote: > On Sat, Sep 13, 2025 at 10:13:19AM -0600, Warner Losh wrote: > > On Sat, Sep 13, 2025 at 10:08=E2=80=AFAM bob prohaska > wrote: > > > > > Is it normal for git to consume (while buildworld is running) close > > > to 1 GB of memory for durations exceeding an hour? > > > > > > More fundamentally, is it OK to start buildworld immediately after > > > a git pull finishes interactive output and returns a shell prompt? > > > > > > > It's what I do: > > > > % git pull --rebase > > % make buildworld > > After running make cleandir twice, buildworld still failed with > the same "failed assertion" error. > > Running > git pull --rebase > reported > Updating 63bd2416ccd..455426da078 with no apparent errors > and a return to the shell prompt. Meanwhile, top continues > to show git activity, some minutes later amounting to over > one GB of memory use, 66MB of swap use and ~80% of one core > in use. After a few more minutes memory use grew to 1.2 GB, > but %CPU is lower, ~10-20%. > > > Top does not show any flags applied to git, and a > ps -aux | grep git > reports only the "grep git" process, nothing else. > > It's very likely that at some point I started buildworld > while git was similarly active. > > Am I correct thinking this would be a bad thing? > Yes. It can be. RPi2, IIRC, has USB2, so having root on usb would mean it's a relatively high latency connection. That's fine, in general, but causes two problems for you. (1) git is very sensitive to high latency I/O path. This means git will run for much longer on such a system and (2) git can take a lot of memory, which is bad during buildworld which itself creates a lot of memory pressure. The two together means that buildworld has a lot less memory to work with and will be slower or may even fail. I'm surprised at the git activity. top only reports the command. It must be in tear-down still (which is weird, because the shell does a wait() for the process and the process is completely torn down before that returns... So I'm super confused... I like the more plausible explanation of 'git was running in another session when I started world' but it does seem like that might not be the case. Warner --00000000000035dd9b063ec57a82 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Sep 14,= 2025 at 10:25=E2=80=AFAM bob prohaska <fbsd@www.zefox.net> wrote:
On Sat, Sep 13, 2025 at 10:13:19AM -0600, Warner Lo= sh wrote:
> On Sat, Sep 13, 2025 at 10:08=E2=80=AFAM bob prohaska <fbsd@www.zefox.net> wrot= e:
>
> > Is it normal for git to consume (while buildworld is running) clo= se
> > to 1 GB of memory for durations exceeding an hour?
> >
> > More fundamentally, is it OK to start buildworld immediately afte= r
> > a git pull finishes interactive output and returns a shell prompt= ?
> >
>
> It's what I do:
>
> % git pull --rebase
> % make buildworld <args>

After running make cleandir twice, buildworld still failed with
the same "failed assertion" error.

Running
git pull --rebase
reported
Updating 63bd2416ccd..455426da078 with no apparent errors
and a return to the shell prompt. Meanwhile, top continues
to show git activity, some minutes later amounting to=C2=A0 over
one GB of memory use, 66MB of swap use and ~80% of one core
in use. After a few more minutes memory use grew to 1.2 GB,
but %CPU is lower, ~10-20%.=C2=A0


Top does not show any flags applied to git, and a
ps -aux | grep git
reports only the "grep git" process, nothing else.

It's very likely that at some point I started buildworld
while git was similarly active.

Am I correct thinking this would be a bad thing?

<= /div>
Yes. It can be. RPi2, IIRC, has USB2, so having root on usb would= mean it's a relatively high latency connection. That's fine, in ge= neral, but causes two problems for you. (1) git is very sensitive to high l= atency I/O path. This means git will run for much longer on such a system a= nd (2) git can take a lot of memory, which is bad during buildworld which i= tself creates a lot of memory pressure. The two together means that buildwo= rld has a lot less memory to work with and will be slower or may even fail.=

I'm surprised at the git activity. top only r= eports the command. It must be in tear-down still (which is weird, because = the shell does a wait() for the process and the process is completely torn = down before that returns... So I'm super confused...

I like the more plausible explanation of 'git was running in ano= ther session when I started world' but it does seem like that might not= be the case.

Warner
--00000000000035dd9b063ec57a82--