Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp3252768pxa; Tue, 18 Aug 2020 10:16:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyYur9ZxhJJXXyUXrqZfk3PLA+zmFKwiMOZM8E+xIojwTymYVTh+1Ris+xVaEpdaFD9siBr X-Received: by 2002:a05:6402:1cb3:: with SMTP id cz19mr20149016edb.299.1597770977559; Tue, 18 Aug 2020 10:16:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597770977; cv=none; d=google.com; s=arc-20160816; b=U8mCeVHUnNKM1iQgnt738PDgX+de/C0N7/7XXWJmti42fU1abhEWCheRlJpuhqUmgJ Ci4q5JqiF8fDSNNS9bkxBFA+MgsJJLtMrcIVpD2l7fjq5EBwLGV9SjLc1z59/XSesKlj nfkHIEZfeu3nBkKMrmScVZ3JiHyWIM9TnqcZSMhHCzWattPunsLNVtL+tLhyQERUPJye EKU29rMeAq+6WjCmV40+JHCz3u80IAU+rhMPBELJV1SU+BUNPCIaErbxz/G02o3nqNLq tpyyTjtuseuImdnZGgDKUAUZOwIjAWubJcOQLMBfISTuURYyO0SVAooEGXA8jbVq1JNI 9o6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=NVSPG5XNKhpGegk/S2rsEcUf1ErS6V+Uzdhp7bPKg7M=; b=ut1gHHb/WG8M3x+9GsgrIkpqLFehPtgxQS/iulvNE/9neLS/2JBWoqpDHzv4Xgzku7 q58LTUxickC0Vw/+c4R22kGw/ltHTcraDkAzDQBegr8I3uBzO4+2LELKyIZX2B3cLnS0 Va7NyhtvPTYohpdOe4yAuJ//FtmL5x7AV3ZzfESECkm21fmsxmnD/KN2R/bMW2GX0qaM OMtytIVu4wkWMDRnzKkupy0eMV8cctvj3ggqAGhqyoNhLtpudPCIDrNvyA7pcottQ5/B B2Mi3fn5esF85oMB/p4PeZvvVa9qYHo8U0JGO0jpRH4v0SCq5qCpfy4fDIm2/m8kDq9Q fGcA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=TTT0Ymfx; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=gejVnZTC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q22si13749336edr.317.2020.08.18.10.15.53; Tue, 18 Aug 2020 10:16:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=TTT0Ymfx; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=gejVnZTC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728394AbgHRROt (ORCPT + 99 others); Tue, 18 Aug 2020 13:14:49 -0400 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]:55069 "EHLO wout4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726836AbgHRROe (ORCPT ); Tue, 18 Aug 2020 13:14:34 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 7D0C510EE; Tue, 18 Aug 2020 13:14:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 18 Aug 2020 13:14:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=fm1; bh=N VSPG5XNKhpGegk/S2rsEcUf1ErS6V+Uzdhp7bPKg7M=; b=TTT0YmfxjtGG1MEEj CDW0flEU9rbHzZUjQ3ehzcO0f+MyAK2+VoTJlpSkXhJ8h9zcPZV6VupJ2EpZVmCR 9sgmiZAmrHIPN13do6bCn4SDkTVfuT+YgwqfprF0d4rfwoG/BF/AuAe6B/bJ0mGe JJ2Bq1dIsIkhIAP1aUmjJOnmMjtYP/YHa8QiTkQ2q32PzK4LICrKKue3agep6PSg JMIN0rnLUYWlROFa3usN2S9BmtJ2N/vyLxu9YblZ9hO8eoUl+WmhgTMtfp2Kew2H lara6kECFpiK4g83u06+4bFsNb8a00s2NL6QL8kmxsI/3eGEIkNWJYSXZfUWURGv D6R5w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=NVSPG5XNKhpGegk/S2rsEcUf1ErS6V+Uzdhp7bPKg 7M=; b=gejVnZTC1JTc58kh30UoJF6jlT1Uqz5KPxrSVBBQlcZYs0+ubxPh6hE+I mP2zFgfxTOYcsg+4VRpC7xDMJQB+ZtOZr6GWdi1sKcm2zj03PKvHAwsn20W/KM+X 8n8XpNRdky2KxthemFANm1rixTscJA3o66Eg+jmyMBlbPJhXhflkMOdOpNe5Ft52 qg4HhVEMQvVVtyiKNbs6qZ2c4Tqe2GL+Y4ccG7F3niso+wAGYQjkeFgLtoXN+tD0 SjpE4AuWryDxBLQ0zNc1LCChzzlVGj9WBO4RrAeWzQYYgzHYjRrUSQ85At5V/k7h 9bmJMTlJLGgYo4TlX9HeLkSZNwzEw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddtiedgkeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjsehtke ertddttdejnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhm qeenucggtffrrghtthgvrhhnpeeuheekheelffefieduteefkeejffdvueehjeejffehle dugfetkedvleekudduvdenucfkphepkeefrdekiedrkeelrddutdejnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A3E83280063; Tue, 18 Aug 2020 13:14:32 -0400 (EDT) Date: Tue, 18 Aug 2020 19:14:57 +0200 From: Greg KH To: Muni Sekhar Cc: kernelnewbies , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org Subject: Re: Scheduler benchmarks Message-ID: <20200818171457.GA736234@kroah.com> References: <20200818143633.GA628293@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 18, 2020 at 10:24:13PM +0530, Muni Sekhar wrote: > On Tue, Aug 18, 2020 at 8:06 PM Greg KH wrote: > > > > On Tue, Aug 18, 2020 at 08:00:11PM +0530, Muni Sekhar wrote: > > > Hi all, > > > > > > I’ve two identical Linux systems with only kernel differences. > > > > What are the differences in the kernels? You didn't answer this question, is this the same kernel source being compared here? Same version? Same compiler? Everything identical? > > > While doing kernel profiling with perf, I got the below mentioned > > > metrics for Scheduler benchmarks. > > > > > > 1st system (older kernel version compared to the other system) benchmark result: > > > > > > $ perf bench sched messaging -g 64 > > > # Running 'sched/messaging' benchmark: > > > # 20 sender and receiver processes per group > > > # 64 groups == 2560 processes run > > > > > > Total time: 2.936 [sec] > > > > > > > > > 2nd system benchmark result: > > > > > > $ perf bench sched messaging -g 64 > > > # Running 'sched/messaging' benchmark: > > > # 20 sender and receiver processes per group > > > # 64 groups == 2560 processes run > > > > > > Total time: 10.074 [sec] > > > > > > > > > So as per scheduler benchmark results, clearly a huge difference > > > between two systems. > > > Can anyone suggest to me how to dive deeper to know the root cause for > > > it. > > > > Look a the differences between your different kernels, that would be a > > great start :) > I created the difference between two kernel config files and then > tried to spot the CONFIG*SCHED* differences. > Interestingly I see the difference in I/O scheduler config, 1st system > is set to “deadline” and other one is set to “cfq”. So I made it equal > by echoing to “/sys/block//queue/scheduler" but still no > change in scheduler benchmark metrics. > > Is it the correct way to find the differences between kernels? If so, > what other important CONFIG_* variables need to consider? > > > $ cat config.patch | grep -i sched > > CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y > CONFIG_CGROUP_SCHED=y > CONFIG_FAIR_GROUP_SCHED=y > # CONFIG_RT_GROUP_SCHED is not set > # IO Schedulers > @@ -369,10 +434,14 @@ CONFIG_IOSCHED_NOOP=y > CONFIG_IOSCHED_DEADLINE=y > CONFIG_IOSCHED_CFQ=y > CONFIG_CFQ_GROUP_IOSCHED=y > -CONFIG_DEFAULT_IOSCHED="deadline" > +CONFIG_DEFAULT_IOSCHED="cfq" > +CONFIG_MQ_IOSCHED_DEADLINE=m > +CONFIG_MQ_IOSCHED_KYBER=m > +CONFIG_IOSCHED_BFQ=m > +CONFIG_BFQ_GROUP_IOSCHED=y > CONFIG_SCHED_SMT=y > CONFIG_SCHED_MC=y > +CONFIG_SCHED_MC_PRIO=y > +# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set > +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y There's lots of other options that affect performance, depending on your specific benchmark, other than these. good luck! greg k-h