-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Cache more stuff #1234
Comments
I fully agree on header detection, it's something I've been thinking about recently. The recent extension correction features fall into this same bucket as well. And I think it will be even more important as I'm adding support for compressed disc images such as CHD and NKit. Can you elaborate more on the "DAT detection" piece? |
Like when IGIR reads the files and makes sure they are valid dats |
Scanning for + parsing the contents of DATs is generally fast unless processing an exceptionally large archive such as TOSEC's. Loading it from a cache file would take roughly the same amount of time, except it would greatly increase the cache file's size. I'll look to focus on the other features soon. |
🔒 Inactive issue lockThis issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Comment generated by the GitHub Lock Issues workflow. |
Is your feature request related to a problem?
I think it would speed things up a lot more if stuff like header detection and DAT detection was cached because right now a lot of these high quantity operations take a lot of time.
Describe the solution you'd like
To cache results of operations so they take less time after the first run.
Additional context
No response
The text was updated successfully, but these errors were encountered: