lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <58289b1c-8a56-4607-8632-d36aef1fc5dd@oracle.com>
Date: Wed, 13 Nov 2024 13:03:00 -0500
From: Joseph Salisbury <joseph.salisbury@...cle.com>
To: peterz@...radead.org, mingo@...nel.org
Cc: juri.lelli@...hat.com, vincent.guittot@...aro.org,
        dietmar.eggemann@....com, Steven Rostedt <rostedt@...dmis.org>,
        bsegall@...gle.com, mgorman@...e.de, vschneid@...hat.com,
        linux-kernel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [REGRESSION] sched/fair: Add lag based placement

Hello,

During performance testing, we found a regression of ~9% performance 
with the TPCC benchmark.   This performance regression was introduced in 
v6.6-rc1.  After a bisect, the following commit was identified as the 
cause of the regression:

86bfbb7ce4f6 ("sched/fair: Add lag based placement")

I was hoping to get some feedback from the scheduler folks.  Do you 
think gathering any additional data will help diagnose this issue?  Are 
there any tunable options that can changed to see how performance is 
affected?


Thanks,

Joe








Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ