From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111987] Unstable performance (periodic and repeating patterns of fps change) and changing VDDGFX
Date: Thu, 17 Oct 2019 13:06:57 +0000 [thread overview]
Message-ID: <bug-111987-502-p7Tf3WirSB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111987-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 855 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111987
--- Comment #14 from Alex Deucher <alexdeucher@gmail.com> ---
You can force the clocks low or high by:
echo low > power_dpm_force_performance_level
or
echo high > power_dpm_force_performance_level
setting it to auto will restore the automatic behavior:
echo auto > power_dpm_force_performance_level
The behavior will depend on the workload. If the workload is really bursty, it
may cause the clocks to ramp up and down if there are sufficiently long idle
periods between workloads. You can manually adjust the heuristics by selecting
the custom profile and tweaking each parameter. See the documentation here:
https://dri.freedesktop.org/docs/drm/gpu/amdgpu.html#gpu-power-thermal-controls-and-monitoring
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1837 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-17 13:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 5:03 [Bug 111987] Unstable performance (periodic and repeating patterns of fps change) and changing VDDGFX bugzilla-daemon
2019-10-13 5:03 ` bugzilla-daemon
2019-10-13 5:04 ` bugzilla-daemon
2019-10-13 5:08 ` bugzilla-daemon
2019-10-13 5:08 ` bugzilla-daemon
2019-10-13 5:13 ` bugzilla-daemon
2019-10-13 5:14 ` bugzilla-daemon
2019-10-13 5:15 ` bugzilla-daemon
2019-10-13 5:24 ` bugzilla-daemon
2019-10-13 9:34 ` bugzilla-daemon
2019-10-13 10:08 ` bugzilla-daemon
2019-10-13 10:25 ` bugzilla-daemon
2019-10-15 20:54 ` bugzilla-daemon
2019-10-16 12:44 ` bugzilla-daemon
2019-10-17 11:51 ` bugzilla-daemon
2019-10-17 13:06 ` bugzilla-daemon [this message]
2019-10-17 18:12 ` bugzilla-daemon
2019-10-17 18:19 ` bugzilla-daemon
2019-10-17 18:41 ` bugzilla-daemon
2019-11-19 9:58 ` 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-111987-502-p7Tf3WirSB@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox