From nobody Fri Oct 27 13:09:45 2023 X-Original-To: freebsd-stable@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 4SH30s5Hl4z4yF8v for ; Fri, 27 Oct 2023 13:09:49 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4SH30r4kCvz4S9P for ; Fri, 27 Oct 2023 13:09:48 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b="n/iZ92VB"; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=B+Nnw6r9; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.25 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 458795C029B for ; Fri, 27 Oct 2023 09:09:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 27 Oct 2023 09:09:48 -0400 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:sender :subject:subject:to:to; s=fm3; t=1698412188; x=1698498588; bh=y9 WYeNA+srVLGRru5R5XN1hrambhPT/FHQWQusCl1EM=; b=n/iZ92VB/15mFTTcxF uEYLc1NtTU2LxhFWez5PIyCTcW32X75mTkB8OVDRSR7RTAj5kPyIHfUqF7thpJFC uDcHLIrUqBaAXw5tKQuyY0gU5BUNyvCpM+KaPds3arQ9CcRotyyavCauYzGPTHM/ I+Ic85H/6z7w+yeRxmqxupiZaVqKDT+5Q3ZuWjhYRBZlC7iw9+M2Dk4sorpHj0B1 hu1DCzbh68gw0DDS8XPnVr70DB/80yTvbZYPT/oGr77NwY8ezB5vct0F3vI4edfK eH5MucBkcE7GfibH8EtYEx96exRkXWTKB/h9nuxhACetfukiImKGjPPJnIvzl1wG P0uA== 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:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1698412188; x=1698498588; bh=y9WYeNA+srVLG Rru5R5XN1hrambhPT/FHQWQusCl1EM=; b=B+Nnw6r9GXKk2/lJEXdS0IkCOts/b mGW0cGugeHI44Avg+i3IjBB5qrEq3xxNpdItpuDKKm5ojQzDyojLL8t7nGmhrscB U/j/KqCGQVzq3lFRogmMSVzF9VLzKeO6Esxyn5YQJgCQSEUjKvtjhqUtK3ehdzp0 0uOrUD/hYyqVBMkQVNMUpeh47jJJltsT2/y+FM7bH4lTgIehlLPzBNd6Xh6yaX+d e8qBEJ6D9GSsI4GIxLw1qVWPdXhNk8R8DwBvCR1+DUH5Fyp+L6Icc/wH3+3aJJef ANIJHvpFU+CdlyCjR3RzesuAv6lv3ToQlZ/KgVSI1fo2L5xaruu1nU3FQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrleeggdeivdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrght thgvrhhnpefhueffheeuhedvjeeuffegffdvueejuddvudfgueeutdeitdetleekvedufe eludenucffohhmrghinhepfhhrvggvsghsugdrohhrghdpvhhnlhhruhdrughirhgvtght pdhsthgrthhsrdhfrhgvvgenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 27 Oct 2023 09:09:47 -0400 (EDT) Date: Fri, 27 Oct 2023 14:09:45 +0100 From: void To: freebsd-stable@freebsd.org Subject: Re: periodic daily takes a very long time to run (14-stable) Message-ID: Mail-Followup-To: freebsd-stable@freebsd.org References: <1122335317.4913.1698407124469@localhost> <2146377145.5323.1698410799235@localhost> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <2146377145.5323.1698410799235@localhost> X-Spamd-Result: default: False [-4.67 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.966]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25:c]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.25:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.25:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SH30r4kCvz4S9P X-Spamd-Bar: ---- On Fri, Oct 27, 2023 at 02:46:39PM +0200, Ronald Klop wrote: >Mmm. Your pool has a lot of space left. So that is good. > >About gstat / iostat, yes during the daily scan would be nice. The numbers outside of the daily scan can also help as a reference. > >NB: There were talks on the ML about vnode re-use problems. But I think that was under a much higher load on the FS. Like 20 find processes in parallel on millions of files. Like this: https://cgit.freebsd.org/src/commit/?id=054f45e026d898bdc8f974d33dd748937dee1d6b and https://cgit.freebsd.org/src/log/?qt=grep&q=vnode&showmsg=1 >These improvements also ended up in 14. OK. This is on stable/14-n265566-4533fa42ad91 arm64 built on Oct 21st and I've verified vfs_subr.o was built on that date. Nothing jumps out at me from sysctl output, but I hardly know a thing about this in particular. What do you think? # sysctl -a | grep vnode kern.maxvnodes: 212370 kern.ipc.umtx_vnode_persistent: 0 vm.vnode_pbufs: 256 vm.stats.vm.v_vnodepgsout: 1825669 vm.stats.vm.v_vnodepgsin: 8165147 vm.stats.vm.v_vnodeout: 59017 vm.stats.vm.v_vnodein: 795355 vfs.wantfreevnodes: 53092 vfs.freevnodes: 95043 vfs.vnodes_created: 40292208 vfs.numvnodes: 102660 vfs.vnode.vnlru.uma_reclaim_calls: 0 vfs.vnode.vnlru.kicks: 0 vfs.vnode.vnlru.max_free_per_call: 10000 vfs.vnode.vnlru.failed_runs: 0 vfs.vnode.vnlru.direct_recycles_free: 12193254 vfs.vnode.vnlru.recycles_free: 13211571 vfs.vnode.vnlru.recycles: 0 vfs.vnode.stats.alloc_sleeps: 0 vfs.vnode.stats.free: 95043 vfs.vnode.stats.skipped_requeues: 1769431 vfs.vnode.stats.created: 40292208 vfs.vnode.stats.count: 102660 vfs.vnode.param.wantfree: 53092 vfs.vnode.param.limit: 212370 vfs.cache.debug.vnodes_cel_3_failures: 0 vfs.cache.stats.heldvnodes: 6383 debug.vnode_domainset: debug.sizeof.vnode: 448 debug.fail_point.status_fill_kinfo_vnode__random_path: off debug.fail_point.fill_kinfo_vnode__random_path: off I let iostat run a while and the following seems representative: device r/s w/s kr/s kw/s ms/r ms/w ms/o ms/t qlen %b da0 100 1 401.4 4.0 70 126 0 70 10 97 pass0 0 0 0.0 0.0 0 0 0 0 0 0 kw/s gets to 700, kr/s 500. Very bursty --