From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218525] New: Thunderbolt eGPU bad performance
Date: Sat, 24 Feb 2024 10:14:18 +0000 [thread overview]
Message-ID: <bug-218525-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218525
Bug ID: 218525
Summary: Thunderbolt eGPU bad performance
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: gipawu@gmail.com
Regression: No
I opened this bug report because I think there is a performance problem in the
Thunderbolt stack.
I have an eGPU R43SG-TB3 adapter, which can be connected either via Thunderbolt
3/4 port, or directly via PCIe M.2 x4 link.
Using the eGPU connected via Thunderbolt, game performance is often absymal,
especially with games that use DXVK.
The problem is described at length here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2885
but in summary, the main symptoms that indicate the presence of a performance
problem with Thunderbolt eGPU are:
- Low and bumpy fps, GPU clock speeds and GPU usage.
- Low or no difference when downscaling the resolution or reducing graphic
settings.
Using the direct M.2 connection instead, performance is as good as expected,
almost on the level of Windows.
In Windows there is a performance gap of 5-10% between Thunderbolt and M.2
connection, but in Linux the gap is much wider, sometimes more than 50%. Very
few games seem to be unaffected by the problem (e.g. Shadows of Tomb Raider and
Doom Eternal).
I tested with an Nvidia RTX 2060 Super GPU, paired with an Intel Nuc 13 Pro
(i5-1340p and Thunderbolt 4) and with a Dell XPS 9570 (i7-8750H and Thunderbolt
3), both running Fedora 39 and kernel 6.7.5. I tried kernel 6.8.0 rc5 too, but
with no differences.
Since the problem emerges with both Nvidia and AMD GPUs (as evident from the
linked report) and that the problem is not reproducible by connecting the GPU
directly via M.2 connection, bypassing the Thunderbolt port, I suspect there is
a performance issue in the Thunderbolt stack, perhaps in proper bandwidth
allocation.
I hope that information given here, and in the link given, may help to resolve
the problem.
I am of course available to provide additional information, logs, and test any
patches if needed. Thank you.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-02-24 10:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 10:14 bugzilla-daemon [this message]
2024-02-24 11:45 ` [Bug 218525] Thunderbolt eGPU bad performance bugzilla-daemon
2024-02-26 6:35 ` bugzilla-daemon
2024-02-29 1:49 ` bugzilla-daemon
2024-02-29 1:50 ` bugzilla-daemon
2024-02-29 1:50 ` bugzilla-daemon
2024-02-29 1:55 ` bugzilla-daemon
2024-02-29 1:55 ` bugzilla-daemon
2024-02-29 9:07 ` bugzilla-daemon
2024-03-01 6:42 ` bugzilla-daemon
2024-03-01 8:59 ` bugzilla-daemon
2024-03-01 9:00 ` bugzilla-daemon
2024-03-01 9:00 ` bugzilla-daemon
2024-03-01 9:39 ` bugzilla-daemon
2024-03-01 9:46 ` bugzilla-daemon
2024-03-06 2:18 ` bugzilla-daemon
2024-03-08 8:17 ` bugzilla-daemon
2024-09-08 12:53 ` bugzilla-daemon
2025-01-06 22:12 ` 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-218525-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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).