search

Paperback-iOS / app

Repository to host app releases, issues, and feature requests for Paperback
https://paperback.moe/
669 stars 21 forks source link

[BUG] Performance issue? #520

Closed henderea closed 2 years ago

henderea commented 2 years ago

Describe the bug On my iPhone, when downloading a lot of chapters, my phone often heats up a lot and drains the battery. I'm not sure if the issue is with the app or with the MangaDex source, but it happens consistently when I'm downloading a lot (and I only do that from MangaDex).

To Reproduce Queue a lot of chapters (probably at least 20 regular length ones to be sure) for download on an iPhone and wait for it to heat up. I suspect cpu monitoring might tell you something too.

Expected behaviour Ideally it wouldn't heat up my phone so much. It also impacts battery life a lot.

App Version 0.7-r24 (though it's been going on for a fairly long time; I can't remember exactly how far back) iPhone 13 Pro Max (though it may not be iPhone-specific; iPads probably just don't heat up as much) iOS 15.4 (and earlier versions) Source: MangaDex ("primary" repo)

Screenshots If applicable, add screenshots to help explain your problem.

FaizanDurrani commented 2 years ago

It's downloading a lot of files and writing them to storage, that's to be expected. Have you tried downloading files over large periods of time with other apps? (ex: Genshin)

henderea commented 2 years ago

Not a whole lot, but I suppose you have a point. Though when I download a lot in the BookWalker Global app, I don't usually see this issue. So it might just be the page-by-page download method. Maybe some sort of grouped download might be better if sources supported it.

FaizanDurrani commented 2 years ago

Source websites aren't really made with downloading in mind so none of them support grouped downloads. BookWalker is its own source for content so they probably have an optimized delivery system that ensures low filesize and efficient content delivery.

github-actions[bot] commented 8 months ago

This 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.