From owner-freebsd-current@freebsd.org Fri Feb 8 09:28:32 2019 Return-Path: Delivered-To: freebsd-current@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 238DB14D9E3D for ; Fri, 8 Feb 2019 09:28:32 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 69921712B9 for ; Fri, 8 Feb 2019 09:28:31 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: by mailman.ysv.freebsd.org (Postfix) id 2D3F714D9E3A; Fri, 8 Feb 2019 09:28:31 +0000 (UTC) Delivered-To: current@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 0933614D9E39 for ; Fri, 8 Feb 2019 09:28:31 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6EEC1712B7 for ; Fri, 8 Feb 2019 09:28:30 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from [192.168.1.32] (unknown [192.168.1.32]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: Alexander@Leidinger.net) by outgoing.leidinger.net (Postfix) with ESMTPSA id 4A909206E; Fri, 8 Feb 2019 10:28:02 +0100 (CET) From: Alexander Leidinger To: "Rodney W. Grimes" , Date: Fri, 08 Feb 2019 10:27:59 +0100 Message-ID: <168cc6f6518.27fa.fa4b1493b064008fe79f0f905b8e5741@Leidinger.net> In-Reply-To: <201902071536.x17FaPtI051105@pdx.rh.CN85.dnsmgr.net> References: <201902071536.x17FaPtI051105@pdx.rh.CN85.dnsmgr.net> Subject: Re: "Oddness" in head since around r343678 or so MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="us-ascii" Content-Transfer-Encoding: 8bit X-Leidinger-net-MailScanner-Information: Please contact the ISP for more information X-Leidinger-net-MailScanner-ID: 145AF1A033.AB269 X-Leidinger-net-MailScanner: Found to be clean X-Leidinger-net-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.999, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, URIBL_BLOCKED 0.00) X-Leidinger-net-MailScanner-From: alexander@leidinger.net X-Leidinger-net-MailScanner-Watermark: 1550222893.8305@eDYSbm8HrryNQ28HfSUtmw X-Leidinger-net-Spam-Status: No X-Rspamd-Queue-Id: 6EEC1712B7 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2019 09:28:32 -0000 Hi, I recently noticed some generic slowness myself. I experienced this during replacing disks in a raidz by bigger ones. Long story short, check top -s if you have vnlru running for a long period at high CPU... If yes increase kern.maxvnodes (I increased to 10 times). Note, we should improve the admin page in the FAQ, the vnlru entry could need a little bit more hints and explanations. If you encounter the same issue we have probably introduced a change somewhere with an unintended side effect. Bye, Alexander. -- Send from a mobile device, please forgive brevity and misspellings. Am 7. Februar 2019 4:43:43 nachm. schrieb "Rodney W. Grimes" : >> I run and track stable/11, stable/12, and head (from separate slices -- >> no VMs involved) on my laptop; among other things, this permits some >> degree of comparison among them. >> >> The laptop is configured to run xdm; while running stable/11 or >> stable/12, there's a period of about 5 seconds after xdm's login banner >> shows up before either the mouse or keyboard responds. >> >> Up to a few days ago, head was the same, but as of about last weekend (I >> think), that period is about 40 seconds while running head. >> >> I realize that's a little ... lacking in specificity, and I apologize >> for that. And while I noticed it a few days ago, I hadn't actually >> timed it until this morning. > > My addition is going to lack even worse, I have been seeing very > long periods of lag, on this 40 second order, when a bhyve instance > is started. The interactive response for this time is 0, not > even ^t produces any output. The prompt comes back almost immediatly > after typing the bhyve command, but that prompt is dead for a > very long time. > > I am running 12.0-RELEASE, and see this issue on multiple machines. > >> >> Information, including verbose dmesg.boot copies and a log of uname >> outputs, may be found from the page at >> . >> >> Here's a list of the uname outputs for head over the last several days: >> >> FreeBSD 13.0-CURRENT #245 r343551M/343551: Tue Jan 29 03:54:46 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #246 r343572M/343572: Wed Jan 30 05:14:44 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #247 r343604M/343604: Thu Jan 31 03:53:37 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #248 r343646M/343658: Fri Feb 1 04:05:45 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #249 r343678M/343678: Sat Feb 2 03:55:23 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #250 r343707M/343711: Sun Feb 3 04:06:08 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #251 r343732M/343741: Mon Feb 4 04:24:07 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #252 r343770M/343771: Tue Feb 5 04:27:38 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #253 r343828M/343834: Wed Feb 6 03:59:36 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> FreeBSD 13.0-CURRENT #254 r343867M/343867: Thu Feb 7 04:52:38 PST 2019 >> root@g1-49.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY >> amd64 1300010 >> >> Peace, >> david >> -- >> David H. Wolfskill david@catwhisker.org >> "It was like reading a Donald Trump tweet. It didn't make any sense." >> >> See http://www.catwhisker.org/~david/publickey.gpg for my public key. > > -- > Rod Grimes rgrimes@freebsd.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"