ChimeraOS / ChimeraOS/chimeraos
Significantly degraded performance after a suspend and resume
- Dominant language
- Shell
- Stars
- 2k
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
Systems tested: OneXPlayer Mini Pro 6800U, Ayaneo 2021
Reproduced on ChimeraOS 42, 43, 44
When entering sleep (either using the power button or the Steam power menu from the in-game overlay) and then resuming, certain games (at least the ones I've checked so far) will run significantly poorer after the resume. On my OneXPlayer Mini Pro 6800U:
- Armored Core 6: prior to sleep average of 30 fps (with Steam's frame cap), after resume the AC assemble screen runs at 9-18 fps.
- Cyberpunk 2077 on Steam Deck preset at 1440x960: prior to sleep average of 30 fps (with in-game frame cap), after resume runs around 12-18 fps.
- Monster Hunter Rise on high preset at 1920x1200: prior to sleep estimated average of 36 fps, after resume runs around 12-18 fps.
Issue persists after quitting and opening the game again, and is only fixed by restarting the system.
I did a fresh install of ChimeraOS and also tried downgrading to 42 and 43, but saw the same phenomenon there.
To see if this was isolated to my OXP, I tried it on my Ayaneo 2021. Cyberpunk 2077 with all settings low or off prior to sleep gives an estimated average of 15fps, after resume runs at an estimated 8-9fps.
I have attached logs from a suspend and resume session, [dmesg.log](https://github.com/ChimeraOS/chimeraos/files/12777110/dmesg.log) and [journalctl.log](https://github.com/ChimeraOS/chimeraos/files/12777111/journalctl.log).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the suspend/resume sequence on the listed OneXPlayer Mini Pro 6800U or Ayaneo 2021 systems, then inspect the attached dmesg.log and journalctl.log files for changes across suspend and resume. Compare performance before and after resuming, including after quitting and reopening a game. Done means the reported performance degradation no longer persists after resume, or the responsible subsystem is identified and documented.
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
- Mostly clear
- Newbie friendliness
- 35/100