Odd performance issue (Raspberry Pi 5)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
When opening content first after opening RetroArch (Apt version on Ubuntu 23.10 on Raspberry Pi 5), performance will be worse than when closing and reopening the content. Specifically, in my case, opening Beetle PSX first will cause severe lag (Doesn't seem to be CPU, audio, shader, or filter related as the same issue happens when all are disabled, and CPU core load doesn't go above 50%) whereas opening any content (even if the core is different, tested with Beetle PSX, FCEUmm and bsnes-mercury Performance) and closing it before opening Beetle PSX will result in no lag. Logs don't seem to show any difference. This seems to only happen in Beetle PSX so it might also be a Beetle issue.
Please note that restarting the content does not fix the issue, only closing and reopening it does.
Expected behavior
Performance should not change significantly between loads.
Actual behavior
First load performance will be worse.
Steps to reproduce the bug
- Open RetroArch
- Load content
- Notice it has performance issues
- Close content
- Reopen the content
- Performance issues are gone
Version/Commit
- RetroArch: 1.17.0
- Git version: r202402040217~fb63c79f32
- Core version: Beetle PSX (0.9.44.10.9.44.1+r202402021331~fb579de8)
Environment information
- OS: Ubuntu 23.10
- Compiler: N/A (apt)
Contributor guide
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
Reproduce the reported sequence on a Raspberry Pi 5 with Ubuntu 23.10: load Beetle PSX first, close it, then load it again, and compare performance and available logs. Check whether the behavior is specific to Beetle PSX or RetroArch's first content load; done means identifying and fixing the first-load performance difference without regressing other cores.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, raspberry-pi, ubuntu
- 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