FR: Improve performance or move slow tasks to background processing

[ajkessel]

I've noticed many actions in ereader lock up the UI until they complete. For example, when I finish an article, I usually select "archive". The article list is then displayed, but I can't interact with it for several seconds until the article is archived and disappears from the list. Sometimes this takes as long as ten seconds.

Is there something happening locally on the device that is slows down the processing step?

Alternatively, couldn't the archive action happen in the background such that I could start reading the next article while the backend Instapaper API call occurs in the background?

[quicklywilliam]

Interesting. These API calls should already be processing in the background, and appear to be working on my device. What hardware are you running?

[ajkessel]

This is a Kobo Libra 2.

I noticed, however, if I disable WiFi, performance is fine. Is it not batching sync operations when WiFi is on and instead doing them in real time?

Is there any logging I could provide that would help diagnose? Or do you want to add some log output that I could test?