Date: Fri, 08 Feb 2019 10:27:59 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>, <current@freebsd.org> Subject: Re: "Oddness" in head since around r343678 or so 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>: >> 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 >> <http://www.catwhisker.org/~david/FreeBSD/history/>. >> >> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?168cc6f6518.27fa.fa4b1493b064008fe79f0f905b8e5741>