From owner-freebsd-arm@freebsd.org Sat Mar 3 00:43:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45BE2F31FC8 for ; Sat, 3 Mar 2018 00:43:26 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D54882A34; Sat, 3 Mar 2018 00:43:25 +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 w230hGF0037371 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 2 Mar 2018 16:43:17 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w230hG8B037370; Fri, 2 Mar 2018 16:43:16 -0800 (PST) (envelope-from fbsd) Date: Fri, 2 Mar 2018 16:43:15 -0800 From: bob prohaska To: Ian Lepore Cc: Warner Losh , Mike , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Is maximum swap usage tunable? Message-ID: <20180303004315.GB37148@www.zefox.net> References: <20180228170311.GA26187@www.zefox.net> <20180228185517.GB26187@www.zefox.net> <8f422161-885e-aa91-eacd-018540222d65@mgm51.com> <20180228214301.GA29481@www.zefox.net> <1520010957.23690.10.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520010957.23690.10.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 00:43:26 -0000 On Fri, Mar 02, 2018 at 10:15:57AM -0700, Ian Lepore wrote: > You forgot a cause: (5) swap is on an sdcard where taking 30-90 seconds > to complete an IO is "normal". > FWIW, the Sandisk Extreme USB flash drive is claimed to be considerably faster than that, ~2MB/sec random write, at least per http://usb.userbenchmark.com/SanDisk-Extreme-USB-30-16GB/Rating/1301 One hopes(!) that the microSD cards of the same name are simlar. > Making it even more fun, there's a sort of (5.5) bullet: an sdcard can > "lend" its horrible performance to every other storage device in the > system. ?If there is a ton of IO queued up to the sd device (such as > when .o files from a a make -j are ending up there) then all the > buffers in the system get stacked up in the sd device's bio queue and > IO to other devices suffers. > A j4 buildworld on an RPI2 running -current seems to work much better than j2 on an RPI3, both using the same Sandisk flash devices. The Pi2 has /usr, /var /tmp and swap on USB flash, the Pi3 has /tmp and half the swap on microSD, with /usr, /var and the other half of swap on USB flash. Thus, /tmp and all of swap are on the same device for the Pi2, while /tmp and only half the swap are on the same device on the Pi3. It was expected the Pi3 should work better than the Pi2, but the opposite seems to be observed. > I've always thought the new(ish) IO scheduler stuff should be able to > help with that in some way, but I never get around to looking at it. > > I'd be pleased to do any testing I can, if it helps. Thanks for reading, bob prohaska