From owner-freebsd-arm@freebsd.org Sat Jul 4 04:37:05 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 0869B361621 for ; Sat, 4 Jul 2020 04:37:05 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49zJvg2FLDz492x for ; Sat, 4 Jul 2020 04:37:02 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 0644b6Qu037430 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 3 Jul 2020 21:37:06 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 0644b61e037429; Fri, 3 Jul 2020 21:37:06 -0700 (PDT) (envelope-from fbsd) Date: Fri, 3 Jul 2020 21:37:05 -0700 From: bob prohaska To: Peter Jeremy Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: 1341MB swap in use with half gig of free memory Message-ID: <20200704043705.GC36886@www.zefox.net> References: <20200703224433.GA36511@www.zefox.net> <20200703233938.GB30039@server.rulingia.com> <20200704011558.GA36886@www.zefox.net> <20200704022218.GD30039@server.rulingia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200704022218.GD30039@server.rulingia.com> X-Rspamd-Queue-Id: 49zJvg2FLDz492x X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [2.39 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.53)[0.534]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.19)[-0.189]; NEURAL_SPAM_LONG(0.15)[0.147]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] 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 04:37:05 -0000 On Sat, Jul 04, 2020 at 12:22:18PM +1000, Peter Jeremy wrote: > 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. > Alas, little about my enterprise is sane 8-) These experiments are all on a Pi3B (not plus). The HDD is attached via a jmicron usb-sata adapter. However, the Pi4 at least in principle claims to support UASP. Unfortunately, it seems FreeBSD does not. That is a pity. > On 2020-Jul-03 18:15:58 -0700, bob prohaska wrote: > >On Sat, Jul 04, 2020 at 09:39:38AM +1000, Peter Jeremy wrote: > > 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. > Up to now I've only restricted -j values when trying to avert panics. Perhaps the experiment is worth a try even if nothing else goes wrong. Have you a notion whether adding additonal swap on microSD would do any good? Earlier experiments included it. This one omitted it by chance, never expecting the build to get this far. Knowing what to look for is helpful. > >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. It appears that links is a close relative of lynx. Both seem to work at www.freebsd.org, but the loss of layout information makes both rather hard to use. Firefox isn't much more compact than chromium, is Safari good anywhere but on a Mac? Edge is new to me. It shows up as /usr/ports/games/edge, but I don't think that's what you meant.... Any hints? Thanks for writing! bob prohaska