From: K Prateek Nayak <kprateek.nayak@amd.com>
To: "Prundeanu, Cristian" <cpru@amazon.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>,
"Saidi, Ali" <alisaidi@amazon.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"Blake, Geoff" <blakgeof@amazon.com>,
"Csoma, Csaba" <csabac@amazon.com>,
"Doebel, Bjoern" <doebel@amazon.de>,
Gautham Shenoy <gautham.shenoy@amd.com>,
Swapnil Sapkal <swapnil.sapkal@amd.com>,
Joseph Salisbury <joseph.salisbury@oracle.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: EEVDF regression still exists
Date: Fri, 2 May 2025 12:03:09 +0530 [thread overview]
Message-ID: <7d3bd258-fa45-4e85-8700-90203bacdeea@amd.com> (raw)
In-Reply-To: <d875adc0-744e-4b1f-a1bf-7e051298a0ae@amd.com>
Hello Cristian,
On 5/2/2025 11:26 AM, K Prateek Nayak wrote:
> Could you also provide some information on your LDG machine - its
> configuration and he kernel it is running (although this shouldn't
> really matter as long as it is same across runs)
So I'm looking at logs at LDG side which is a 4th Generation EPYC system
with 192CPUs running the repro on baremetal and I see:
[20250502.061627] [INFO] STARTING TEST
[20250502.061627] [INFO] 768 VU
...
Vuser 2:VU 2 : Assigning WID=1 based on VU count 768, Warehouses = 24 (1 out of 1)
Vuser 2:Processing 1000000000000 transactions with output suppressed...
...
Now that is equal to 4 * 192CPUs that my LDG has which means I might
need to match the same configuration as your LDG to mimic your exact
scenario.
768VU each processing 1000000000000 transactions sent to a 16vCPU
SUT instance seems like a highly overloaded (and unrealistic) scenario
but perhaps your LDG is also a similar 16vCPU instance which caps the
VU at 64?
Currently doing a trial run, staring at logs to see what I need to
adjust based on the errors. I'll adjust the LDG based on your comments
and try to reproduce the scenario over the weekend.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2025-05-02 6:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 21:38 EEVDF regression still exists Cristian Prundeanu
2025-04-29 21:56 ` Peter Zijlstra
2025-04-29 22:06 ` Prundeanu, Cristian
2025-04-30 3:33 ` K Prateek Nayak
2025-05-01 16:16 ` Prundeanu, Cristian
2025-05-02 5:56 ` K Prateek Nayak
2025-05-02 6:33 ` K Prateek Nayak [this message]
2025-05-02 18:06 ` Prundeanu, Cristian
2025-05-02 8:48 ` Peter Zijlstra
2025-05-02 16:52 ` Prundeanu, Cristian
2025-05-14 21:26 ` Dietmar Eggemann
2025-04-30 10:02 ` Peter Zijlstra
2025-05-02 7:08 ` Sapkal, Swapnil
2025-05-02 17:25 ` Prundeanu, Cristian
2025-05-02 17:52 ` Linus Torvalds
2025-05-03 3:34 ` K Prateek Nayak
2025-05-21 13:30 ` Cristian Prundeanu
-- strict thread matches above, loose matches on Subject: below --
2025-05-20 18:14 Cristian Prundeanu
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=7d3bd258-fa45-4e85-8700-90203bacdeea@amd.com \
--to=kprateek.nayak@amd.com \
--cc=abuehaze@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=blakgeof@amazon.com \
--cc=bp@alien8.de \
--cc=cpru@amazon.com \
--cc=csabac@amazon.com \
--cc=dietmar.eggemann@arm.com \
--cc=doebel@amazon.de \
--cc=gautham.shenoy@amd.com \
--cc=joseph.salisbury@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=swapnil.sapkal@amd.com \
--cc=x86@kernel.org \
/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