ValveSoftware / ValveSoftware/Proton
Threadripper Performance Problem and Workaround
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Proton would eat up all of the Threadripper threads and push the utilization to 75% to 100% on all of the threads and you would notice a low fps game-play on any game that run on Proton.
The workaround is:
Taskset command didn't work for me when I try to restrict the number of cores that process should be allowed to have/access, so another way is that you need to use the maxcpus option in Grub (append on Linux kernel line) and have integer set to about 4 to 8. This problem is specific to Threadripper and it affects all games that run on Proton.
When rebooting with grub, simply press 'e' on highlighted boot menu item and append the maxcpus option like so in grub:
linux ....... maxcpus=4
And simply press ctrl + x after editing the grub boot configuration, login to your favorite desktop manager then bring up System Monitor (any should be fine, I use Gnome System Monitor) to confirm that there are 4 or so cpus running and you can simply try running your game in proton as normal and see if this works.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Begin by reproducing the Threadripper behavior with Proton and compare normal execution with the GRUB maxcpus workaround, using a system monitor to confirm CPU utilization; done would require identifying and addressing the cause or documenting why the workaround is necessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100