From nobody Sat Dec 23 12:36:50 2023 X-Original-To: freebsd-fs@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 4Sy3Zx2QN8z54SLy for ; Sat, 23 Dec 2023 12:37:13 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sy3Zw0bx4z4ZBP for ; Sat, 23 Dec 2023 12:37:12 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b="KjTnzs/v"; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=hQAF7k6D; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E786C5C00EC for ; Sat, 23 Dec 2023 07:37:10 -0500 (EST) Received: from imap46 ([10.202.2.96]) by compute6.internal (MEProxy); Sat, 23 Dec 2023 07:37:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1703335030; x=1703421430; bh=CVqhpzUCnW /D1MgF2GRcut0q3D7CMZkkFJx8Z07Ea7s=; b=KjTnzs/v1UHq+h5x6BHPVYm/dy 2puMQKR6TbBP5MktQC3VNtYNkRgK2fHpa70gvGvU/KTNrclYPrTPe7Ke/EFkZgiG iYpajiEV6U9fJb6Gql5lkcoa+lRj+dviQMR3ifoUHV0WSodyY3P39yBgyszL4fvB snls4008uZiRChQX44cNfrEswstXYquH7c+mTgmU6hXlPbrrpMakORAH43WTKmVM /4ACG687+Pz8hZBLrImltcfelm4/vTfa7Sbo0WQ68MeiUJ8M+YJQi9lZnnhflmwT 9uPznoNhtMpnDbfKt1jqNOuslVxpHgYgGuHWNZ8lmoorp/nhb/jXHV6EbFTA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1703335030; x=1703421430; bh=CVqhpzUCnW/D1MgF2GRcut0q3D7C MZkkFJx8Z07Ea7s=; b=hQAF7k6DUbZAqMT1ZvXrT+8X0A0d7MKrH1VsGrkXdmcj In7pySmkQJfSq7NITma3Q9RwFLRkCBCG7846XnE+3wvDuPUFP+b8/ntL/5TU8mOW AH1RlzmBiJSWv/T2Mr82O0rGH8SbNeYre/F6b5LutRhCdV0R7cyCjrS1+iNhWgW9 oP3NhRURv6KqD60yrahFCIYYwL0QvwgaihF/0Hsj6/mZZT/znRQ2bzYgMFR97RBo ZIP8MbrxrwwRkO+Rf/71GwJoqAX+Hsx3vXQudsLqtYjy3gAVW0f51n26Uw8P1fZX Bg8QD1wKOTA92TslbQRNqLsHVfLGTgyH5cGN2M8YpA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdduledggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffr rghtthgvrhhnpeeitedvueehtdehtddvhfeuhfevhedvieelvdeiffehveelheegfedule ejudekvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id ACB8B2A2008B; Sat, 23 Dec 2023 07:37:10 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1364-ga51d5fd3b7-fm-20231219.001-ga51d5fd3 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 Message-Id: <271589cd-102b-4035-bc0b-1bceba240b66@app.fastmail.com> In-Reply-To: References: <84A99C91-9DB2-4611-A040-2261C1C46CDE@yahoo.com> Date: Sat, 23 Dec 2023 12:36:50 +0000 From: void To: freebsd-fs Subject: Re: measuring swap partition speed Content-Type: text/plain X-Spamd-Result: default: False [-4.17 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.982]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; XM_UA_NO_VERSION(0.01)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[f-m.fm]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org] X-Rspamd-Queue-Id: 4Sy3Zw0bx4z4ZBP X-Spamd-Bar: ---- On Fri, 22 Dec 2023, at 20:08, Mark Millard wrote: > I normally use -j$(sysctl -n hw.ncpu) for installworld but, > if I gather right, you effectively used -j1 (implicit), so > I'll do both styles, -j4 being appropriate for RPi4B's. Interesting. Advice long ago was to not use -j for the installworld part so I've never used it at that stage. Other ways of testing, in place of 'make installworld': git -C /usr/ports pull --ff-only periodic daily find / -name "*.core" -mtime +2 -ls (snip results) > Compared/contrasted to yours, it again suggests seek-time as a > potential notable contribution to the results in your context: > the spinnig rust spends far more overall time between command, > limiting the command processing rate. Plugging in and using a > separate USB3 SSD suitable for use as swap might be a help, > despite the shared bandwidth for the 2 USB3 ports. Even using > the USB2 port could be useful, and might have a more independent > bandwidth. Historically there's been an issue (I didn't delve into it deeply at the time) where if both ports on the usb2 bus were occupied (like keyboard+mouse), one knocks the other off the bus. Doesn't matter what make/model the keyboard or bus are. This was last identified when the system was at 13-stable. At present, there is a wifi module plugged into the usb2 bus (ralink, shows up as run0). It'll page down and up when the system gets busy, to the extent i've had to take it out of monitoring. It's the only thing plugged into the usb2 bus. I've avoided having to plug in more than one usb2 device into this bus since encountering the problem. Having two things plugged into it makes one or the other malfunction. Having one thing plugged into it flaps when the system gets busy. It's unknown to me at this stage whether anything similar affects the usb3 bus. Right now, there's the usb3 disk plugged into one port and a usb2 serial cable (for a UPS) into the other. Something might be affecting usb in general and I've till now considered it to be usb2-only because that's where it was most obvious. So I'm thinking what I'm seeing might be some effect with usb2 and/or 3 being the root cause. Things I'll be trying: 1. creating a swap partition on a usb3 stick plugged into the usb3 bus and running the tests 2. take the disk, plug it into an amd64 usb3 bus, try the tests on the plugged-in disk thanks for your help, it's appreciated.