From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>, Chen Yu <yu.c.chen@intel.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Mel Gorman <mgorman@techsingularity.net>,
Tim Chen <tim.c.chen@intel.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Abel Wu <wuyun.abel@bytedance.com>,
Yicong Yang <yangyicong@hisilicon.com>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
Honglei Wang <wanghonglei@didichuxing.com>,
Len Brown <len.brown@intel.com>, Chen Yu <yu.chen.surf@gmail.com>,
Tianchen Ding <dtcccc@linux.alibaba.com>,
Joel Fernandes <joel@joelfernandes.org>,
Josh Don <joshdon@google.com>,
kernel test robot <yujie.liu@intel.com>,
Arjan Van De Ven <arjan.van.de.ven@intel.com>,
Aaron Lu <aaron.lu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/2] sched/fair: Introduce SIS_CURRENT to wake up short task on current CPU
Date: Mon, 01 May 2023 17:32:05 +0200 [thread overview]
Message-ID: <ce70393575869d65449a59d321a109f10ac82676.camel@gmx.de> (raw)
In-Reply-To: <20230501134827.GB1597538@hirez.programming.kicks-ass.net>
On Mon, 2023-05-01 at 15:48 +0200, Peter Zijlstra wrote:
>
> Throughput 646.55 MB/sec 2 clients 2 procs max_latency=0.104 ms
> Throughput 1361.06 MB/sec 5 clients 5 procs max_latency=0.100 ms
> Throughput 1889.82 MB/sec 10 clients 10 procs max_latency=0.154 ms
> Throughput 2406.57 MB/sec 20 clients 20 procs max_latency=3.667 ms
> Throughput 2318.00 MB/sec 40 clients 40 procs max_latency=0.390 ms
> Throughput 2384.85 MB/sec 80 clients 80 procs max_latency=1.371 ms
>
>
> So what's going on here? I don't see anything exciting happening at the
> 40 mark. At the same time, I can't seem to reproduce Mike's latency pile
> up either :/
Are you running tbench in the GUI so the per second output stimulates
assorted goo? I'm using KDE fwtw.
Caught this from my raspberry pi, tbench placement looks lovely, the
llvmpipe thingies otoh..
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P COMMAND
19109 git 20 0 23468 1920 1664 R 52.65 0.012 3:59.64 4 tbench
19110 git 20 0 23468 1664 1536 R 52.65 0.010 4:00.03 3 tbench
19104 git 20 0 23468 1664 1536 R 52.32 0.010 4:00.15 1 tbench
19105 git 20 0 23468 1664 1536 R 52.32 0.010 4:00.16 0 tbench
19108 git 20 0 23468 1792 1664 R 52.32 0.011 4:00.12 7 tbench
19111 git 20 0 23468 1792 1664 R 51.99 0.011 4:00.33 5 tbench
19106 git 20 0 23468 1664 1536 R 51.66 0.010 3:59.40 6 tbench
19107 git 20 0 23468 1664 1536 R 51.32 0.010 3:59.72 2 tbench
19114 git 20 0 6748 896 768 R 46.69 0.006 3:32.77 6 tbench_srv
19116 git 20 0 6748 768 768 S 46.69 0.005 3:32.17 7 tbench_srv
19118 git 20 0 6748 768 768 S 46.69 0.005 3:31.70 3 tbench_srv
19117 git 20 0 6748 768 768 S 46.36 0.005 3:32.99 4 tbench_srv
19112 git 20 0 6748 768 768 S 46.03 0.005 3:32.51 1 tbench_srv
19113 git 20 0 6748 768 768 R 46.03 0.005 3:32.48 0 tbench_srv
19119 git 20 0 6748 768 768 S 46.03 0.005 3:31.93 5 tbench_srv
19115 git 20 0 6748 768 768 R 45.70 0.005 3:32.70 2 tbench_srv
2492 root 20 0 392608 110044 70276 S 1.987 0.682 8:06.86 3 X
2860 root 20 0 2557284 183260 138568 S 0.662 1.135 2:06.38 6 llvmpipe-1
2861 root 20 0 2557284 183260 138568 S 0.662 1.135 2:06.44 6 llvmpipe-2
2863 root 20 0 2557284 183260 138568 S 0.662 1.135 2:04.94 6 llvmpipe-4
2864 root 20 0 2557284 183260 138568 S 0.662 1.135 2:04.72 6 llvmpipe-5
2866 root 20 0 2557284 183260 138568 S 0.662 1.135 2:04.49 6 llvmpipe-7
19562 root 20 0 26192 4876 3596 R 0.662 0.030 0:00.43 5 top
2837 root 20 0 2557284 183260 138568 S 0.331 1.135 1:51.39 5 kwin_x11
2859 root 20 0 2557284 183260 138568 S 0.331 1.135 2:07.56 6 llvmpipe-0
2862 root 20 0 2557284 183260 138568 S 0.331 1.135 2:05.97 6 llvmpipe-3
2865 root 20 0 2557284 183260 138568 S 0.331 1.135 2:03.84 6 llvmpipe-6
2966 root 20 0 3829152 323000 174992 S 0.331 2.001 0:12.71 4 llvmpipe-7
2998 root 20 0 1126332 116960 78032 S 0.331 0.725 0:25.58 3 konsole
next prev parent reply other threads:[~2023-05-01 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 23:15 [PATCH v8 0/2] " Chen Yu
2023-04-28 23:16 ` [PATCH v8 1/2] sched/fair: Record the average duration of a task Chen Yu
2023-04-28 23:16 ` [PATCH v8 2/2] sched/fair: Introduce SIS_CURRENT to wake up short task on current CPU Chen Yu
2023-04-29 19:34 ` Mike Galbraith
2023-05-01 8:25 ` Peter Zijlstra
2023-05-01 15:15 ` Chen Yu
2023-05-01 13:48 ` Peter Zijlstra
2023-05-01 15:32 ` Mike Galbraith [this message]
2023-05-01 15:37 ` Mike Galbraith
2023-05-01 18:49 ` Peter Zijlstra
2023-05-02 2:51 ` Mike Galbraith
2023-05-01 15:52 ` Chen Yu
2023-05-02 11:54 ` Peter Zijlstra
2023-05-04 11:07 ` Chen Yu
2023-05-12 8:29 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce70393575869d65449a59d321a109f10ac82676.camel@gmx.de \
--to=efault@gmx.de \
--cc=aaron.lu@intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=dtcccc@linux.alibaba.com \
--cc=gautham.shenoy@amd.com \
--cc=joel@joelfernandes.org \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=wanghonglei@didichuxing.com \
--cc=wuyun.abel@bytedance.com \
--cc=yangyicong@hisilicon.com \
--cc=yu.c.chen@intel.com \
--cc=yu.chen.surf@gmail.com \
--cc=yujie.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®