From: K Prateek Nayak <kprateek.nayak@amd.com>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Joel Fernandes <joelaf@google.com>,
Qais Yousef <qyousef@google.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Zimuzo Ezeozue <zezeozue@google.com>,
Youssef Esmat <youssefesmat@google.com>,
Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Metin Kaya <Metin.Kaya@arm.com>,
Xuewen Yan <xuewen.yan94@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
kernel-team@android.com
Subject: Re: [RESEND][PATCH v8 0/7] Preparatory changes for Proxy Execution v8
Date: Thu, 29 Feb 2024 12:14:21 +0530 [thread overview]
Message-ID: <7daee7bc-bf4c-ab24-dbf2-467371ee72e1@amd.com> (raw)
In-Reply-To: <CANDhNCrkXF0R1Otu_EKY6OHxnAOYUQ+UjaQsJ_mW4Ys4ELPcYA@mail.gmail.com>
Hello John,
On 2/29/2024 11:49 AM, John Stultz wrote:
> On Wed, Feb 28, 2024 at 9:37 AM 'K Prateek Nayak' via kernel-team
> <kernel-team@android.com> wrote:
>> I got a chance to test the whole of v8 patches on the same dual socket
>> 3rd Generation EPYC system:
>>
>> tl;dr
>>
>> - There is a slight regression in hackbench but instead of the 10x
>> blowup seen previously, it is only around 5% with overloaded case
>> not regressing at all.
>>
>> - A small but consistent (~2-3%) regression is seen in tbench and
>> netperf.
>
> Once again, thank you so much for your testing and reporting of the
> data! I really appreciate it!
>
> Do you mind sharing exactly how you're running the benchmarks? (I'd
> like to try to reproduce these locally (though my machine is much
> smaller).
>
> I'm guessing the hackbench one is the same command you shared earlier with v6?
Yup it is same as earlier. I'll list all the commands down below:
o Hackbench
perf bench sched messaging -p -t -l 100000 -g <# of groups>
o Old schbench
git://git.kernel.org/pub/scm/linux/kernel/git/mason/schbench.git
at commit e4aa540 ("Make sure rps isn't zero in auto_rps mode.")
schbench -m 2 -t <# workers> -r 30
(I should probably upgrade this to the latest! Let me get on it)
o tbench (https://www.samba.org/ftp/tridge/dbench/dbench-4.0.tar.gz)
nohup tbench_srv 0 &
tbench -c client.txt -t 60 <# clients> 127.0.0.1
o Stream (https://www.cs.virginia.edu/stream/FTP/Code/)
export ARRAY_SIZE=128000000; # 4 * Local L3 size
gcc -DSTREAM_ARRAY_SIZE=$ARRAY_SIZE -DNTIMES=<Loops internally> -fopenmp -O2 stream.c -o stream
export OMP_NUM_THREADS=16; # Number of CCX on my machine
./stream;
o netperf
netserver -L 127.0.0.1
for i in `seq 0 1 <num clients>`;
do
netperf -H 127.0.0.1 -t TCP_RR -l 100 -- -r 100 -k REQUEST_SIZE,RESPONSE_SIZE,ELAPSED_TIME,THROUGHPUT,THROUGHPUT_UNITS,MIN_LATENCY,MEAN_LATENCY,P50_LATENCY,P90_LATENCY,P99_LATENCY,MAX_LATENCY,STDDEV_LATENCY&
done
wait;
o Unixbench (from mmtest)
./run-mmtests.sh --no-monitor --config configs/config-workload-unixbench
--
If you have any other question, please do let me know :)
>
> thanks
> -john
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2024-02-29 6:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 0:11 [RESEND][PATCH v8 0/7] Preparatory changes for Proxy Execution v8 John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 1/7] locking/mutex: Remove wakeups from under mutex::wait_lock John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 2/7] locking/mutex: Make mutex::wait_lock irq safe John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 3/7] locking/mutex: Expose __mutex_owner() John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 4/7] sched: Add do_push_task helper John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 5/7] sched: Consolidate pick_*_task to task_is_pushable helper John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 6/7] sched: Split out __schedule() deactivate task logic into a helper John Stultz
2024-02-24 0:11 ` [RESEND][PATCH v8 7/7] sched: Split scheduler and execution contexts John Stultz
2024-02-28 4:43 ` [RESEND][PATCH v8 0/7] Preparatory changes for Proxy Execution v8 K Prateek Nayak
2024-02-28 4:51 ` John Stultz
2024-02-28 5:12 ` K Prateek Nayak
2024-02-28 5:24 ` John Stultz
2024-02-28 17:37 ` K Prateek Nayak
2024-02-29 6:19 ` John Stultz
2024-02-29 6:44 ` K Prateek Nayak [this message]
2024-02-29 6:55 ` John Stultz
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=7daee7bc-bf4c-ab24-dbf2-467371ee72e1@amd.com \
--to=kprateek.nayak@amd.com \
--cc=Metin.Kaya@arm.com \
--cc=boqun.feng@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=youssefesmat@google.com \
--cc=zezeozue@google.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