From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Olivier Dion <odion@efficios.com>,
michael.christie@oracle.com
Subject: Re: [RFC PATCH v8] sched: Fix performance regression introduced by mm_cid
Date: Tue, 18 Apr 2023 14:24:39 -0400 [thread overview]
Message-ID: <a340030b-ce07-72e8-ba41-2896b31b4f1f@efficios.com> (raw)
In-Reply-To: <40689cd1-af60-542d-2245-c6362c73a365@efficios.com>
On 2023-04-18 12:01, Mathieu Desnoyers wrote:
> On 2023-04-18 07:21, Aaron Lu wrote:
>> On Mon, Apr 17, 2023 at 11:08:31AM -0400, Mathieu Desnoyers wrote:
>>> Introduce per-mm/cpu current concurrency id (mm_cid) to fix a PostgreSQL
>>> sysbench regression reported by Aaron Lu.
>>
>> For postgres_sysbench on SPR:
>> sched_mm_cid_migrate_to() is in the range of 0.1x% - 0.4x%, mm_cid_get()
>> is in the range of 0.1x% - 0.3x%. Other cid functions are pretty minor.
>>
>> For hackbench on SPR:
>> ched_mm_cid_migrate_to() is about 3%-4%, mm_cid_get() is about 7%-8%,
>> other cid functions are pretty minor.
>
> It's a bit higher than I would have expected for hackbench.
>
> Can you run with the attached schedstats patch applied and boot
> with schedstats=enable ? Let me know how the counters behave please,
> because I cannot reproduce anything unexpected on my machine.
>
Also, just to confirm, do you still use this hackbench invocation ?
hackbench --pipe --threads -l 500000
Thanks,
Mathieu
> Thanks,
>
> Mathieu
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2023-04-18 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 15:08 Mathieu Desnoyers
2023-04-18 11:21 ` Aaron Lu
2023-04-18 16:01 ` Mathieu Desnoyers
2023-04-18 18:24 ` Mathieu Desnoyers [this message]
2023-04-19 8:06 ` Aaron Lu
2023-04-19 13:10 ` Mathieu Desnoyers
2023-04-20 6:00 ` Aaron Lu
2023-04-20 12:38 ` Mathieu Desnoyers
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=a340030b-ce07-72e8-ba41-2896b31b4f1f@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=aaron.lu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=odion@efficios.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®