Optimize restore backup
Opened this issue · 6 comments
Describe your suggested feature
Usually Komikku (as well as most of other forks) takes at least 50 minutes to restore a backup. J2K and their forks takes 10 minutes maximum. The reason for that is SAF (at least that is what someone from the mihon discord server told me)
What they explained is:
"But basically, the idea is, because SAF is really slow, you want to make SAF calls as less as possible.
Such as use one call to retrieve all metadata you need for files under a directory instead of doing them one by one."
Also, tyvm for opening the issues tab! I appreciate it.
Other details
No response
Acknowledgements
- I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
- I have written a short but informative title.
- If this is an issue with an official extension, I should be opening an issue in the extensions repository.
- I have updated the app to version 1.10.5.
- I will fill out all of the requested information in this form.
Thanks for the info. Will definitely look into it.
Just to give a side by side comparison.
Both of them contain the same amount of entries.
Just to give a side by side comparison. Both of them contain the same amount of entries.
how is Mihon doing?
Just to give a side by side comparison. Both of them contain the same amount of entries.
how is Mihon doing?
testing rn
I'll send a screenshot when its finished
Just to give a side by side comparison. Both of them contain the same amount of entries.
how is Mihon doing?
@cuong-tran
Did a Yokai restore as well because my library has changed a lot since the first image
just including how much time it took to sync on pc