Quote:
Originally Posted by JimmXinu
What's the benefit?
The BG job already launches a separate process for each site--limited by the number of CPUs Calibre reports, which Calibre also does to BG jobs.
The downsides are additional complexity and getting more than one 'Proceed to update library' dialog as each BG job ends. Which I'm sure will confuse some users, even if it's an option they have to turn on.
|
Well, if something goes wrong with one of the websites (that results in FFF spinning it's wheels forever instead of erroring out, like with the fastnovel thing I posted), it doesn't mess up the download from the other sites.
Also, I have a 24-core (48-thread) ThreadRipper system. Based on the messages in the FlareSolverr window, I can say with absolutely certainty that on my system it never downloads anything in parallel.
(Also that, if I cancel the job because of that fastnovel thing, the job is shown as canceled after a few seconds, while in the background it will happily continue to download 2000+ chapters if I don't kill FlareSolverr.)
If I start separate jobs for the different websites by hand, it always finishes much faster than if I try to just start a single job for all the books I want to update.
Also, showing multiple 'Proceed to update library' messages is a feature not a bug. That way, once the first site finishes, I can start reading the new chapters while the other downloads are still running instead of waiting another 20 minutes or so for all of them to finish.