From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215729] amd-pstate driver has a much higher idle power consumption for a desktop Zen 3 CPU
Date: Wed, 23 Mar 2022 15:58:30 +0000 [thread overview]
Message-ID: <bug-215729-137361-v3CuNhVnWI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215729-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215729
--- Comment #6 from Artem S. Tashkinov (aros@gmx.com) ---
After rebooting again with amd-pstate the situation has kinda improved:
Max CPU frequency in idle is now around 1.2GHz with occasional spikes to
2.2GHz.
Power consumption is now around 23W - not a big difference with acpi-cpufreq
but I was under the impression that amd-pstate should be more power efficient,
not less.
'Minimum' governor is now at around ~20W in idle which matches acpi-cpufreq.
----
Here's the most important thing:
The ondemand governor in idle makes the CPU consume around 23.5W
The performance governor in idle makes the CPU consume around 20.5W which is
near perfect.
So, it looks like the ondemand governor falters with amd-pstate for some
reasons. Maybe it does more work than necessary, maybe it gets called far too
often, I've no idea.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-03-23 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 23:58 [Bug 215729] New: amd-pstate driver has a much higher idle power consumption for a desktop Zen 3 CPU bugzilla-daemon
2022-03-22 23:59 ` [Bug 215729] " bugzilla-daemon
2022-03-23 0:01 ` bugzilla-daemon
2022-03-23 2:09 ` bugzilla-daemon
2022-03-23 15:35 ` bugzilla-daemon
2022-03-23 15:41 ` bugzilla-daemon
2022-03-23 15:58 ` bugzilla-daemon [this message]
2022-03-23 16:04 ` bugzilla-daemon
2022-04-28 8:49 ` bugzilla-daemon
2022-05-09 8:38 ` bugzilla-daemon
2023-07-07 13:24 ` bugzilla-daemon
2023-09-15 10:24 ` bugzilla-daemon
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=bug-215729-137361-v3CuNhVnWI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.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;
as well as URLs for NNTP newsgroup(s).