Date: Fri, 22 Mar 2024 15:47:02 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 275594] High CPU usage by arc_prune; analysis and fix Message-ID: <bug-275594-3630-pq1GtkZm74@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275594-3630@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275594 --- Comment #94 from Felix Palmen <zirias@freebsd.org> --- (In reply to Felix Palmen from comment #89) > will continue to observe the overall behavior. After a pretty busy (for my ZFS pool) week with the patches applied, I'd say the behavior is very good now. Provoking stalls requires crazy things like multiple poudriere-builds in I/O heavy phases (like *-depends) at the same time and also doing other I/O (e.g. in bhyve VMs). A "normal" bulk build with full parallel jobs *and* MAKE_JOBS allowed is barely noticeable when scheduled on idprio. As I said, it was always sub-optimal on 13.x, but became utterly unusable with 13.3-RELEASE. What I forgot to mention is: on 13.3, there were even EBADFs suddenly popping up for build jobs, which could very well be some "hidden" bug that's only triggered by excessively bad performance... All in all, I personally think this issue desperately needs fixing; depending on your hardware(?) and workload pattern, you can't really use 13.3 without patches right now. Is anyone active reviewing the code? -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275594-3630-pq1GtkZm74>