Date: Tue, 23 Jul 2019 12:43:49 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Jamie Landeg-Jones <jamie@catflap.org> Cc: freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: Lethargic rpi3, but seemingly still running Message-ID: <20190723194349.GA32898@www.zefox.net> In-Reply-To: <201907230419.x6N4JRYZ069168@donotpassgo.dyslexicfish.net> References: <20190718034838.GA1921@www.zefox.net> <201907180958.x6I9wBF8075274@donotpassgo.dyslexicfish.net> <20190718151858.GB4325@www.zefox.net> <20190718182050.GL2342@funkthat.com> <20190721005135.GA18642@www.zefox.net> <201907230419.x6N4JRYZ069168@donotpassgo.dyslexicfish.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 23, 2019 at 05:19:27AM +0100, Jamie Landeg-Jones wrote: > bob prohaska <fbsd@www.zefox.net> wrote: > > > Here's a snippet of systat -v 1 output while un-tarring firefox files. > > %busy was close to zero, it looks like there's congestion or a deadlock > > writing to the microSD card. At the time things like cd and ls were > > very slow to respond (tens of seconds) > > > > 28 pdpgs cpu2:ast > > Disks mmcsd da0 pass0 intrn cpu3:ast > > KB/t 12.00 0.00 0.00 152904 wire 9 cpu0:preem > > tps 5 0 0 80072 act 51 cpu1:preem > > MB/s 0.06 0.00 0.00 671344 inact 80 cpu2:preem > > %busy 213 0 0 120 21104 27 cpu3:preem > > You say "close to zero", but it's 213(!) in the output you gave! > Sorry, I was referring the %idle number above the bargraph and inverting the fraction, without noticing the %busy in the Disks output. At the moment the same machine is compiling clang8 with about 900M of swap in use, here is another sample: Disks mmcsd da0 pass0 264 intrn cpu3:ast KB/t 5.51 5.77 0.00 169680 wire 641 cpu0:pree tps 461 457 0 645096 act 1612 cpu1:pree MB/s 2.48 2.58 0.00 2280 inact 1522 cpu2:pree %busy 77 50 0 Swap is on both mmcsd and da0 (Samsung Evo+ microsd and a Sandisk usb3 flash drive). > However, I suspected something like that - high %busy whilst little actual > transfers taking place. I've seen it before, along with the characteristics > you describe, but unfortunately I don't have a fix. > So far I think the problem has only been obvious when bsdtar is running. If there's another way to provoke it that might be interesting to try. Thanks for reading more closely than I wrote! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190723194349.GA32898>