Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.0.24-14127 Huge slowdown and wrong memory allocation crashing OS #12661

Closed
Augusto7743 opened this issue Sep 15, 2022 · 11 comments · Fixed by #12700
Closed

0.0.24-14127 Huge slowdown and wrong memory allocation crashing OS #12661

Augusto7743 opened this issue Sep 15, 2022 · 11 comments · Fixed by #12700

Comments

@Augusto7743
Copy link

Augusto7743 commented Sep 15, 2022

Quick summary

Hello.
Thanks for reading my topic.
I seeing here huge slowdown for some games.
CPU AMD FX-6300 4 GB RAM Geforce GT 640 driver 470.129.06
Linux Ubuntu 20.04.5 64 bits.
An old cpu, but only reporting an huge slowdown since 0.0.24-14127.
Perhaps that issue is happening in other cpus too.

Testing using 0.0.24-14124 and 0.0.24-14127 games below are having 100 % gameplay speed, but are using almost 15 % more cpu usage.

Bionic Commando Rearmed [NPUB30022]
Bomberman ULTRA [NPUB30051]
Spelunker HD [NPUB30152]
TMNT: Turtles In Time Re-Shelled [NPUB30107]

Comparing RPCS3 current version and several previous versions now current version is less gpu usage and almost 15 % less VRAM usage too. Thanks very much !

0.0.24-14124 testing the games below have good speed improvements if comparing with several previous versions and use all cpu cores.

Burnout Paradise V1.9 [NPUB30040] average above 25 FPS
MOTORSTORM PACIFIC RIFT DEMO [NPUA70022] average 14 FPS.
LittleBigPlanet [NPUA80472] run above 25 FPS. Several previous versions was less of 10 FPS.

Now 0.0.24-14127 has an huge slowdown for games below, not using all cpus cores and crashing RPCS3.

Burnout Paradise V1.9 [NPUB30040] crash at title screen "press start button" using totally RAM memory and swap file in few seconds. Not is possible start the game.

LittleBigPlanet [NPUA80472] randomly crash loading in "video scenes" using totally RAM memory and swap file in few seconds. Gameplay is less of 4 FPS and not using all cpus cores.

MOTORSTORM PACIFIC RIFT DEMO [NPUA70022] less of 4 FPS with graphics issues and not using all cpus cores.

RPCS3 in few seconds from 2,46 GB RAM usage goes to use all RAM memory and swap file at point crashing the OS too.
Seeing in task manager RPCS3 not is using all 6 cores. Few cores are being used and only 1 core is totally used (possibly PPU) and others are less 50 % used.
0.0.24-14124 use all cpu cores and not does wrong memory allocation.

0.0.24-14127 randomly is crashing in "Building SPU Cache" screen closing RPCS3.
The problem is 0.0.24-14127 12603 simd_builder ver. 2
#12603

Logs are below.
Please if need any log or rsx capture reply.
Have an nice day.

Details

No response

Attach a log file

Burnout Paradise.zip
Burnout Paradise ASMJIT.zip
LittleBigPlanet.zip
LittleBigPlanet Disable Vulkan Memory Allocator.zip
MOTORSTORM PACIFIC RIFT DEMO.zip

Attach capture files for visual issues

No response

System configuration

No response

Other details

No response

@Nerboruto
Copy link

put more ram 4gb are too few..
motorstorm runs at 25 / 30fps on one of my pc with 8gb ddr3 xeon e3-1230v3 quad core haswell 3.3ghz gtx 745 2gb ddr3..

@AniLeo
Copy link
Member

AniLeo commented Sep 17, 2022

I think we should go for setting minimum RAM requirement at 8 GB

@elad335
Copy link
Contributor

elad335 commented Sep 17, 2022

Hi, does #12443 work for you?

@solarmystic
Copy link

solarmystic commented Sep 19, 2022

Between 0.0.24-14106 and 0.0.24-14148 happening anything destroying the performance, not allowing cpus cores being used totally and allocating huge memory size crashing the OS.

@Augusto7743 There are around 20 builds between 14106 and 14148, and anyone of these could have caused your issue.

pg2

pg1

If you want a fix to this issue, you have to narrow down the exact build/PR that caused the huge slowdown/crashes for you, a large range of builds is not helpful at al. The developers cannot be expected to do this precise regression testing in order to determine the exact build that caused your issue, you have to provide it for them.

Here's a quick guide to regression testing from the bot at the rpcs3 discord:-

image

@Augusto7743 Augusto7743 changed the title 0.0.24-14148 huge slowdown, crash using all RAM and others issues 0.0.24-14127 Huge slowdown and wrong memory allocation crashing OS Sep 23, 2022
@Augusto7743
Copy link
Author

Edited the summary with more correct information.

@Augusto7743
Copy link
Author

I think we should go for setting minimum RAM requirement at 8 GB

0.0.24-14123 RAM usage (OS + RPCS3 LLVM)

Burnout Paradise 2,94 GB
GOWA 2,76 GB only in first stages, but after the number of shaders will be high requiring more than 6 GB RAM.
LittleBigPlanet 2,35 GB
MOTORSTORM PACIFIC RIFT DEMO 2,74 GB

For Linux 4 GB RAM still is enough, but perhaps for others OS the requirement is more than 6 GB.

@solarmystic
Copy link

solarmystic commented Sep 24, 2022

Just encountered another user who gets massive slowdown in Tekken 6 that can be traced back to the very same build (0.0.24-14127) #12603

The user has an i7 3770/GTX 1060 machine which was running the game perfectly at 60 fps with no slowdowns in any stage using the build right before 14127 which is 0,0,24-14124.

https://discord.com/channels/272035812277878785/277227681836302338/1023193718741807134

The common denominator between the author of this report's rig and that user's rig is that both are on CPUs that do not have AVX2 support, only AVX, which is quite fascinating to say the least.

Their logfile:-
RPCS3.log

The massive slowdown persists on their rig until the current master and is not fixed by #12624

unknown

@Yahfz
Copy link
Contributor

Yahfz commented Sep 24, 2022

If the issue is only triggered on a CPU without AVX2, you can just set the LLVM target to sandybridge in the configfile and see if you can reproduce it.

@Nekotekina
Copy link
Member

I'll look into it.

@Augusto7743
Copy link
Author

Tested 0.0.24-14183 with some games.
Not more huge slowdown and wrong memory allocation =)
Thanks very much =)

For others games the PR 11904 (vm locking refactoring) in current build continue breaking the GOWA performance having an huge slowdown.
PR 11904 date is 2022-05-02 and being from several previous builds has anyone analyzing it ?
#11904

@Mainak009
Copy link

Just encountered another user who gets massive slowdown in Tekken 6 that can be traced back to the very same build (0.0.24-14127) #12603

The user has an i7 3770/GTX 1060 machine which was running the game perfectly at 60 fps with no slowdowns in any stage using the build right before 14127 which is 0,0,24-14124.

https://discord.com/channels/272035812277878785/277227681836302338/1023193718741807134

The common denominator between the author of this report's rig and that user's rig is that both are on CPUs that do not have AVX2 support, only AVX, which is quite fascinating to say the least.

Their logfile:-
RPCS3.log

The massive slowdown persists on their rig until the current master and is not fixed by #12624

unknown

I faced this same slowdown too when using inside batocera.linux....tekken 6 loading, menu, intro video fine around 60 fps but when characters render it drops to around 10-15 FPS.....my hardware is i5-3550 3.7ghz, Nvidia GT710 2gb, Ram 4gb×2 ddr3 1333Mhz.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants