All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207667] New: power_dpm_force_performance_level set to "low" reduces CPU performance (Vega 8 / Ryzen 2200G)
Date: Sat, 09 May 2020 20:48:35 +0000	[thread overview]
Message-ID: <bug-207667-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=207667

            Bug ID: 207667
           Summary: power_dpm_force_performance_level set to "low" reduces
                    CPU performance (Vega 8 / Ryzen 2200G)
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.6.8
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: alekshs@hotmail.com
        Regression: No

I've been on a power saving quest lately, trying various different things. One
of the things that I don't particularly need in my Ryzen 2200G is GPU
performance. So it made sense to reduce the 400 MHz clock to lower levels to
gain in power efficiency.

I echoed "low" to power_dpm_force_performance_level and indeed my power
consumption dropped while the frequency went down from 400MHz to 200MHz. I now
see Vsoc went from 1.01v to 0.91v and Isoc went from 3.5A to 1.75A.

What I did not expect was that I would see performance issues in terms of CPU
tasks.

CPU tasks like SHA256 hashing are unaffected.
CPU tasks that involve RAM, like lrzip, cinebench 15 (under wine), etc, show a
considerable drop in performance. CB15 cpu score loses >10% while an lrzip file
compression went from 14 to 21 seconds. I also did a geekbench 5 comparison
(more of that in the end - with links).

I measured cache and memory bandwidth, it seems to be the same whether I have
power_dpm_force_performance_level set to low or auto, so downclocking the
integrated graphics of the ryzen didn't impact memory speeds. Maybe it's an
interactivity thing / irq thing or something that makes tasks wait? Or maybe
it's a power delay issue as the SOC has to increase watts on demand? I don't
know - someone has to find out.

I think it's abnormal behavior for the IGP clock to cause CPU applications to
slow down - especially by more than 50% in some cases:

I've run 2 geekbench 5.0 benchmarks, with the only difference being "low" and
"auto" on the power_dpm_force_performance_level:

Low: https://browser.geekbench.com/v5/cpu/2096508
Auto: https://browser.geekbench.com/v5/cpu/2096537

If you scroll down you see some tasks are very heavily affected while others
aren't.

For example multithreaded raytracing is at 4900 in both instances. But
multithreaded speech recognition is 900 vs 1800, while AES is 2100 vs 4500.
Huge differences.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-05-09 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 20:48 bugzilla-daemon [this message]
2020-05-14  5:47 ` [Bug 207667] power_dpm_force_performance_level set to "low" reduces CPU performance (Vega 8 / Ryzen 2200G) 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-207667-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.