From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fra-out-006.esa.eu-central-1.outbound.mail-perimeter.amazon.com (fra-out-006.esa.eu-central-1.outbound.mail-perimeter.amazon.com [18.197.217.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8D92B32E122 for ; Wed, 4 Feb 2026 13:59:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=18.197.217.180 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770213586; cv=none; b=e6eIg1Nv73sXOT9/yCK3aSD23uTADCJdSxL77m405SH/MNHC86M3fjLH3G8LI2DlNZK4+UQ8wbXRlWskS96rLii5Wk+7aqebcBe3KQKw+HrbW/mqHGwcHTcbbmTZ2DROr3kaB3tQmFkLWXhAlEGZql6QeG+nak/7bXgi5LvZ6Rs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770213586; c=relaxed/simple; bh=6A5KmSKpow11X4M8U/GfM7g84aovuBFfyhktHq0AOCk=; h=Subject:Message-ID:Date:MIME-Version:To:CC:References:From: In-Reply-To:Content-Type; b=s/3hy+jxjiYJQKNid09wdYuli9L6b3/oO/glDym4RUWUS3/UI/MK/QbczOqIgAICKoizCkzt5j+3YKLQyFqm1sjYvZrBiCrJ+Sxh/hAsYWhLyWe3GmoUEGl4b+ErpViGFi8m2jq8G0S4Na0OxrpJw+1tdmoHF/mOb1FcfUbS8SU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=amazon.com; spf=pass smtp.mailfrom=amazon.com; dkim=pass (2048-bit key) header.d=amazon.com header.i=@amazon.com header.b=pJzoh83E; arc=none smtp.client-ip=18.197.217.180 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=amazon.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=amazon.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=amazon.com header.i=@amazon.com header.b="pJzoh83E" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazoncorp2; t=1770213585; x=1801749585; h=message-id:date:mime-version:to:cc:references:from: in-reply-to:content-transfer-encoding:subject; bh=gIpz9SOwsVmaL5YjQ8FGLPr0OQxqfTWtwdPeB/2P36U=; b=pJzoh83EMz8uTewijcorwRIkBQqP59TRteMJx4iFaOAPO6h4LMmvfAr7 ZECIqX2kLJ03Fqrieugk31RiCn3iIQ7GEfS2R36Q/GD0vXdhnKJYztSZp Dsm49L+8rwa3mUab6VjeLU/c5609VSAoXp6yYiM8B30m4LBAtSfh5hg0T PVzsa8c/3nAcKA97O6/T768fNvdDWfcue1tQFUlNLEB3Gb9OoMMw0t4y+ +Oi4xbFThwBVMdtlQvHS1gdEAfcVrn3wVuxEBOyl23oe9Njk0tbWwG9CM pX/+3CQj/jMWlJulOWDktJa+EkEiNm8eYl/yyEuObnhFLmfWDbC7+dFzT w==; X-CSE-ConnectionGUID: A5c55b7aQqipSG4tSqCpgw== X-CSE-MsgGUID: zOO679LNRumzpdvHS/iM0g== X-IronPort-AV: E=Sophos;i="6.21,272,1763424000"; d="scan'208";a="8931795" Subject: Re: [PATCH 4/4] sched/fair: Proportional newidle balance Received: from ip-10-6-6-97.eu-central-1.compute.internal (HELO smtpout.naws.eu-central-1.prod.farcaster.email.amazon.dev) ([10.6.6.97]) by internal-fra-out-006.esa.eu-central-1.outbound.mail-perimeter.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Feb 2026 13:59:27 +0000 Received: from EX19MTAEUC002.ant.amazon.com [54.240.197.228:28096] by smtpin.naws.eu-central-1.prod.farcaster.email.amazon.dev [10.0.40.102:2525] with esmtp (Farcaster) id a7bbc0ea-6a93-4a61-bec5-fb463968c3d3; Wed, 4 Feb 2026 13:59:26 +0000 (UTC) X-Farcaster-Flow-ID: a7bbc0ea-6a93-4a61-bec5-fb463968c3d3 Received: from EX19D018EUA004.ant.amazon.com (10.252.50.85) by EX19MTAEUC002.ant.amazon.com (10.252.51.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.2562.35; Wed, 4 Feb 2026 13:59:26 +0000 Received: from [192.168.1.220] (10.106.83.33) by EX19D018EUA004.ant.amazon.com (10.252.50.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.2562.35; Wed, 4 Feb 2026 13:59:25 +0000 Message-ID: Date: Wed, 4 Feb 2026 13:59:24 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Peter Zijlstra CC: Mario Roy , Chris Mason , "Joseph Salisbury" , Adam Li , Josh Don , , , , , , , , , References: <20251107161739.770122091@infradead.org> <8760001e-0274-454c-a4e4-1f38a9695b88@gmail.com> <3ef2a178-db96-4a2c-9e74-44ba81bef030@amazon.com> <20260127084412.GV171111@noisy.programming.kicks-ass.net> <20260129091937.GY166857@noisy.programming.kicks-ass.net> <683b4860-1076-43b8-8fb9-ca8ac26cd8f4@amazon.com> <20260202105144.GC1282955@noisy.programming.kicks-ass.net> <6237f4ee-6b07-4d79-8ee7-04e49a4e99b7@amazon.com> <20260204132710.GK2995752@noisy.programming.kicks-ass.net> Content-Language: en-US From: "Mohamed Abuelfotoh, Hazem" In-Reply-To: <20260204132710.GK2995752@noisy.programming.kicks-ass.net> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: EX19D006EUC002.ant.amazon.com (10.252.51.238) To EX19D018EUA004.ant.amazon.com (10.252.50.85) On 04/02/2026 13:27, Peter Zijlstra wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. > > > > On Wed, Feb 04, 2026 at 12:45:41PM +0000, Mohamed Abuelfotoh, Hazem wrote: > >> Version | Benchmark name | SUT EC2 Instance| diff % >> v6.12.66 | postgresql | c7a.4xlarge | -4.0% >> v6.12.66 | nginx_lb | c7a.4xlarge | -5.0% >> v6.12.66 | memcached | c7a.4xlarge | -11.0% >> v6.12.66_proposed | postgresql | c7a.4xlarge | -4.0% >> v6.12.66_proposed | nginx_lb | c7a.4xlarge | -5.0% >> v6.12.66_proposed | memcached | c7a.4xlarge | -13.0% > > *sigh*, that actually made it worse for memcached :/ I'm not familiar > with the memcached benchmark, is this something I can run on a single > machine, or does it require high speed networking and 2 machines? Yup that's true it's slightly worse on memcached with the proposed fix:( The memcached benchmark is kind of multi-layer test where you need at at least 2 client machines and 1 server machine and 1 machine as a test coordinator. The server VM is able to achieve 12.5 Gbps of network bandwidth and the client each one is able to achieve 30 Gbps so I think it will be tricky and likely impossible to reproduce this on a single machine. I will try to come-up with standalone reproduction steps that can be used to investigate this memcached regression. Meanwhile we will share the fio regression reproduction steps that I mentioned in my previous update. This should be much simpler in steps and can be done on a single machine.