From owner-freebsd-arm@freebsd.org Sat Jul 4 02:22:34 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E4A0535F2A0 for ; Sat, 4 Jul 2020 02:22:34 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49zFwT6sMjz433j for ; Sat, 4 Jul 2020 02:22:33 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id 0642MOso098849 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 4 Jul 2020 12:22:29 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id 0642MIaH029804 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Jul 2020 12:22:18 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id 0642MIne029803; Sat, 4 Jul 2020 12:22:18 +1000 (AEST) (envelope-from peter) Date: Sat, 4 Jul 2020 12:22:18 +1000 From: Peter Jeremy To: bob prohaska Cc: freebsd-arm@freebsd.org Subject: Re: 1341MB swap in use with half gig of free memory Message-ID: <20200704022218.GD30039@server.rulingia.com> References: <20200703224433.GA36511@www.zefox.net> <20200703233938.GB30039@server.rulingia.com> <20200704011558.GA36886@www.zefox.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="t0UkRYy7tHLRMCai" Content-Disposition: inline In-Reply-To: <20200704011558.GA36886@www.zefox.net> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp X-Rspamd-Queue-Id: 49zFwT6sMjz433j X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@rulingia.com designates 2001:19f0:5801:ebe:5400:1ff:fe53:30fd as permitted sender) smtp.mailfrom=peter@rulingia.com X-Spamd-Result: default: False [-5.51 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.02)[-1.018]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.02)[-1.015]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[rulingia.com]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.08)[-1.078]; RCPT_COUNT_TWO(0.00)[2]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5800::/38, country:US]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2020 02:22:35 -0000 --t0UkRYy7tHLRMCai Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Something I missed before: When you say "Pi3", I presume you mean Raspberry Pi 3 Model B. None of the Raspberry Pi variants have provision for sanely attaching mass storage so I presume your 1TB HDD is attached via USB 2.0 - which is a further impediment to tranferring data fast. On 2020-Jul-03 18:15:58 -0700, bob prohaska wrote: >On Sat, Jul 04, 2020 at 09:39:38AM +1000, Peter Jeremy wrote: >In this case (essentially that of a batch job with no interactive use) >would using -j1 or -j2 reduce the overall compilation time? If I'm=20 >understanding correctly the answer is "no", -j1 precludes using extra=20 >cores when it's possible. From time to time it uses all four.=20 As Mark mentions, about the only real way to find out would be to actually try building with different -j options and see which is fastest. So long as the total working set size remains below the ~800MB usable RAM limit then more cores will speed it up. Once the system starts thrashing then goodput[1] drops to roughly zero. Unfortunately, the working set size varies widely. >A smaller browser would be a very welcome discovery. So far, chromium >is the only one that has worked well enough to be useful. If you just want to render HTML, images and some trivial JS, then something like links might do. Unfortunately, the modern Web has shifted to the point where the HTML is irrelevant and the actual content is mostly the result of executing quite complex JS within the browser - for those pages, you'll probably need Chrom{e,ium}, Edge, Firefox or Safari. [1] Useful throughput --=20 Peter Jeremy --t0UkRYy7tHLRMCai Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE2M6l8vfIeOACl4uUHZIUommfjLIFAl7/59RfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQ4 Q0VBNUYyRjdDODc4RTAwMjk3OEI5NDFEOTIxNEEyNjk5RjhDQjIACgkQHZIUommf jLLyGBAAsY6mFrOvl8Ui4v6rnOvH+I6s7/mvjnkNkbnR/FEHCI9sS17eP5Hxp/H7 c9N+oh7vhKf06T0jQ3Nvi0oqJyz1lIzNRU7HURYVAQkxxTGzSi4917v6K9S+834o OJcl/Sa0j1qFMVu3+j3S5FTH5UsdwxQWwG2EzCw+4+niOmoAJi1+BkMewqs10UiQ sa+N6LnfJHt+GTiSFbs6V5t+evUtpe9pRdApgxIe2s8IwwcrG6VlWBV+nWzJqXDa dKoeQ+NlDV4NZWcwcCEvRxSeegPRGVq6AY32UTTyPotJKrtqLglLVmKPZONq/Zut WyO8kkPFQ4wZ3EQAjyBoMXp6KQWcFK+K4mmzISwUOa6psL0L9Z2b3lwD5j7XzadX Y8JrG6dhOhW0Ubh5iw+ZW1BrCa3l7zIHmYu8ZYvzS0ROol+oPzqNaqMFf+4nGj4r qqAFER6kI0L6UYX1nySXZTOltbUPfVceVErkwt5rxTGT0ddFVJqD+w+L2iqFMbug DtBDV5jD6Xn/9mBxd7JFtLz6OXWrulmNOnCBkGBaidZhdLioUEpPOWAdeDKcqz/d Wvryv3BG8zRgxW72TQREO3Fw6P1WG0/dqM5lWFZ5cCTAWjDIq+nVIqaXGdqmar7p 5qmbTnoxI/YI+gkKraEeUoIBExkML5gBVVzBKT2K1D1q4VpkCaA= =F+cz -----END PGP SIGNATURE----- --t0UkRYy7tHLRMCai--