-
Notifications
You must be signed in to change notification settings - Fork 165
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
Parallelize refresh work #963
Comments
That's great! I am still wondered how you can implement everything so quick. |
Just FYI, I had to switch back to serial update checking for background tasks. I'm not sure why but the parallel method seemed to cause some silent crash a lot of the time. Foreground checking (pull to refresh) still uses the parallel method and (which is the main UX improvement for this issue anyways - I'm guessing most people aren't checking how long background updates take). I'll try messing around with the BG process again at some point. |
That doesn't seem to have fixed it. Might be an Android 14 issue (switched to it on both devices shortly after this change). If either of you are on Android <14 did you have any issues with parallel checking in the background task? |
Yeah, parallel updates weren't the issue - will switch back to them in the next release. Not sure why the tasks are crashing so often on my devices. |
Will track the task crashes on the existing issue #608 |
Is your feature request related to a problem? Please describe.
I have 31 apps registered in Obtainium. Refreshing the full app list takes a few minutes. This is also caused by some app entries taking a bit longer to refresh.
Describe the feature
I think the refresh speed could be increased by parallelizing the network requests to all the app sources. Right now due to the speed it seems like only one app source would be fetched at once.
The text was updated successfully, but these errors were encountered: