From nobody Wed Aug 16 16:48:00 2023 X-Original-To: current@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 4RQvG8288xz4qr0f for ; Wed, 16 Aug 2023 16:48:16 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RQvG76tWNz3K5w for ; Wed, 16 Aug 2023 16:48:15 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none Received: from webmail2.leidinger.net (roundcube.Leidinger.net [192.168.1.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: Alexander@Leidinger.net) by outgoing.leidinger.net (Postfix) with ESMTPSA id 2902159B; Wed, 16 Aug 2023 18:48:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1692204483; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4w0yYgiwwb1dOPSHF9IKJHnD2O5IEFufwWdP4EdgAFs=; b=iKXH6Oj2wSsWb0rxe0auCVJWUbCIy/yPC5oAM/FutcAkEavaj/SOOp6VivwKDBcVBX6DCb xxXnjdfoTrQm8cMAH+usx54TQDCGZAONNrE9TL7D7xY/X+eg+AzIYsto2Rs9/85ovuye6U mczxUmMZVTW1sDg1lVv9koBinuD3azqVZ3LbfuwJY0SloE+WxGf2EIFvJ5mjCeME2ZmQG0 o/c+AWQ3rK5qjqSxzpiPRc8AjeQVAZ0/7iCg+64KikNRboW1ph7q6F7fPLvVYwr4/nU+dZ fik6mC7AO96tBKcEDTQo3cy1r+iI3mX0WaeX2397yZ2wo3UQCo+vrfrsQmGnhg== List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Wed, 16 Aug 2023 18:48:00 +0200 From: Alexander Leidinger To: Mateusz Guzik Cc: current@freebsd.org Subject: Re: Speed improvements in ZFS In-Reply-To: References: <61ca9df1b15c0e5477ff51196d0ec073@Leidinger.net> Message-ID: <88e837aeb5a65c1f001de2077fb7bcbd@Leidinger.net> X-Sender: Alexander@Leidinger.net Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4RQvG76tWNz3K5w X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] Am 2023-08-15 23:29, schrieb Mateusz Guzik: > On 8/15/23, Alexander Leidinger wrote: >> Am 2023-08-15 14:41, schrieb Mateusz Guzik: >> >>> With this in mind can you provide: sysctl kern.maxvnodes >>> vfs.wantfreevnodes vfs.freevnodes vfs.vnodes_created vfs.numvnodes >>> vfs.recycles_free vfs.recycles >> >> After a reboot: >> kern.maxvnodes: 10485760 >> vfs.wantfreevnodes: 2621440 >> vfs.freevnodes: 24696 >> vfs.vnodes_created: 1658162 >> vfs.numvnodes: 173937 >> vfs.recycles_free: 0 >> vfs.recycles: 0 New values after one rund of periodic: kern.maxvnodes: 10485760 vfs.wantfreevnodes: 2621440 vfs.freevnodes: 356202 vfs.vnodes_created: 427696288 vfs.numvnodes: 532620 vfs.recycles_free: 20213257 vfs.recycles: 0 >>> Meanwhile if there is tons of recycles, you can damage control by >>> bumping kern.maxvnodes. What's the difference between recycles and recycles_free? Does the above count as bumping the maxvnodes? >> Looks like there are not much free directly after the reboot. I will >> check the values tomorrow after the periodic run again and maybe >> increase by 10 or 100 so see if it makes a difference. >> >>> If this is not the problem you can use dtrace to figure it out. >> >> dtrace-count on vnlru_read_freevnodes() and vnlru_free_locked()? Or >> something else? >> > > I mean checking where find is spending time instead of speculating. > > There is no productized way to do it so to speak, but the following > crapper should be good enough: [script] I will let it run this night. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF