Skip to content

Auto Splitters: Add optional cache for memory mappings #45

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

Merged
merged 1 commit into from
Jun 2, 2024

Conversation

EXtremeExploit
Copy link
Collaborator

@EXtremeExploit EXtremeExploit commented May 13, 2024

Mainly an experimental feature (i think values 0 and 1 shouldnt be experimental since i havent seen any problem with them) i liked to see for some games that dont have a fixed game state update rate where a lot of reads happen and its VERY important to have a super accurate timer. More info is included in the docs

Performance

Performance is taken from 150 samples on a script that reads on the same module 10 times. Numbers are in microseconds

mapsCacheCycles Average min max
0 (default) 8555 6850 15930
1 1148 948 3934
2 631 122 1417

Notes:

  • Because values higher than 1 make some cycles completely cached the results oscillate between completely cached and 1 cache missed like this:
    image

  • Also i added the documentation for getPID on the documentation

  • And an extra check for type string in case the user specifies (or doesnt) an invalid string size

@wins1ey wins1ey merged commit 318c78e into wins1ey:main Jun 2, 2024
1 check passed
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 this pull request may close these issues.

2 participants