From owner-freebsd-bugs@freebsd.org Thu Jan 9 11:00:01 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 329421E9902 for ; Thu, 9 Jan 2020 11:00:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47tjnF0dQyz3xsF for ; Thu, 9 Jan 2020 11:00:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 138EF1E9901; Thu, 9 Jan 2020 11:00:01 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 123CE1E9900 for ; Thu, 9 Jan 2020 11:00:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47tjnD6bgRz3xsD for ; Thu, 9 Jan 2020 11:00:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DDED027AE2 for ; Thu, 9 Jan 2020 11:00:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 009B00K0026055 for ; Thu, 9 Jan 2020 11:00:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 009B00Vj026053 for bugs@FreeBSD.org; Thu, 9 Jan 2020 11:00:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 243212] High CPU usage when set affinity on multiple CPU Date: Thu, 09 Jan 2020 11:00:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pizzamig@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2020 11:00:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243212 Bug ID: 243212 Summary: High CPU usage when set affinity on multiple CPU Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: pizzamig@freebsd.org We are facing a minor, but disturbing regression, when we moved from FreeBSD 11.3 to 12.1 on our loadbalancers. We have 2 identical machines (dual CPU, 4 core per CPU), one running FreeBSD 11.3 and one running 12.1.=20 Identical packages and identical configuration. We have a haproxy instance and, for performance reasons, we pin the threads= to different cpus: nbproc 1 nbthread 6 cpu-map auto:1/1-6 0-5 The result of this configuration is (on 11.3): # cpuset -g -p 35799 pid 35799 mask: 0, 1, 2, 3, 4, 5 while on 12.1 is: # cpuset -g -p 86498 pid 86498 mask: 0, 1, 2, 3, 4, 5 pid 86498 domain policy: first-touch mask: 0, 1 What we have seen is a increased CPU usage (2x) and system load (almost doubled) on FreeBSD 12.1. We didn't measure a potential impact on the netwo= rk latency. A way to solve/workaround the issue is to decrease the number of threads to= 4. I guess that this regression has something to do with NUMA, maybe threads 4= ,5 are forced to use memory domain 0, causing the additional CPU usage. Is this intended? If yes, why on FreeBSD 11.3 we don't see this high CPU us= age? Thanks in advance for the help I report here some hardware information. hw.model: Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz hw.ncpu: 8 kern.sched.topology_spec: 0, 1, 2, 3, 4, 5, 6, 7 0, 1, 2, 3 0 1 2 3 4, 5, 6, 7 4 5 6 7 --=20 You are receiving this mail because: You are the assignee for the bug.=