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

JitArm64: Allocate 64 MB for farcode #10267

Merged
merged 1 commit into from Dec 16, 2021

Conversation

JosJuice
Copy link
Member

@JosJuice JosJuice commented Dec 8, 2021

My change in 867cd99 caused farcode to fill up much more than before. Most games still ran fine, but certain games would have multiple cache clears per minute, on top of being overall slow.

Maybe there's something prettier we can do about this than just allocating more RAM, but we have the resource budget for making Dolphin use more RAM, so I consider increasing the size of the cache to be a good solution at least for the time being.

At least for Prince of Persia: The Forgotten Sands, 48 MB isn't enough to stop the cache clears, but 64 MB is. (I only played the game for a few minutes when testing, though.)

My change in 867cd99 caused farcode to fill up much more than before.
Most games still ran fine, but certain games would have multiple
cache clears per minute, on top of being overall slow.

Maybe there's something prettier we can do about this than just
allocating more RAM, but we have the resource budget for making
Dolphin use more RAM, so I consider increasing the size of the
cache to be a good solution at least for the time being.

At least for Prince of Persia: The Forgotten Sands, 48 MB isn't
enough to stop the cache clears, but 64 MB is. (I only played the
game for a few minutes when testing, though.)
@brujo5
Copy link

brujo5 commented Dec 9, 2021

Confirmed this PR Fixed slowndowns for me. Thx

@degasus degasus merged commit 80ccb20 into dolphin-emu:master Dec 16, 2021
10 checks passed
@JosJuice JosJuice deleted the jitarm64-bigger-farcode branch December 16, 2021 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants