All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 13 Oct 2019 05:08:30 +0000	[thread overview]
Message-ID: <bug-111987-502-OGUUCCheS9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111987-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1323 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111987

--- Comment #3 from Witold Baryluk <witold.baryluk+freedesktop@gmail.com> ---
I initially blamed OBS (Open Broadcasting Studio) for the problem. But I was
able to reproduce the issue even with OBS recording, previewing, grabbing
frame, or even it running.

So I am almost sure it is hardware or power management issue in kernel driver.

Unfortunately I am not quite able to capture timelines of the
/sys/kernel/debug/dri/0/amdgpu_pm_info correlated with the frametimes, as very
often reading this sysfs file will block all the rendering for few
milliseconds, skewing results (frametime spikes).

However, I can tell that the temperature reported there is constantly below 32
deg C, and frequency looks all the time the same, at least for the GPU core.

The voltage and GPU load reported there is all over the place, sometimes
reporting 0% GPU load, despite the game running in windowed mode and producing
200 FPS, which should be at least ~30% GPU load from my other measurements.

I also confirmed FPS / frametimes issues with 3 other independent methods
(DXVK_HUD=fps, GALLIUM_HUD=fps, in-game fps / frametime counters). But main one
is using modified Mesa overlay.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2203 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

  parent reply	other threads:[~2019-10-13  5:08 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 [this message]
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
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-OGUUCCheS9@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 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.