http://bugs.gpodder.org/show_bug.cgi?id=293
--- Comment #6 from Justin Forest <[email protected]> 2009-01-15 11:08:23 --- (In reply to comment #5) > The timeout solution can work if we are allowed to update the database (i.e. > call db.commit() from another thread). This would also have the advantage of > not having to freeze the UI for the short time that the database is updated > (might get a bit longer than < 1 sec. on Maemo or Netbooks). This would also have a disadvantage of having yet another thread, which is bad for machines with limited resources. I've seen how drasitically idle downloader threads slow down my netbook, so I vote "no thanks". The amount of data written to the database after an episode is downloaded, or marked for not downloading, or something like that, is very low. I don't believe it would slow down the UI so bad that an extra thread would be a better solution. I don't think we need to optimize this without benchmarking first. Besides, I have yet to see gPodder hanging so bad that I have to kill it. If this really happens that often, an investigation is necessary, until then I'd stay with the current solution. -- Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
