http://bugs.gpodder.org/show_bug.cgi?id=293
--- Comment #7 from Thomas Perl <[email protected]> 2009-01-16 19:27:29 --- Ok, a separate thread is probably overkill. But there is the case where you start downloading similarly-sized episodes of the same podcast at the same time, and (depending on a lot of factors) they mostly happen to finish at the same time, needing many separate DB writes. I'd rather have the requestor of a "commit" set a dirty flag and if the flag has not yet been set, start a timer (e.g. via gobject.timeout_add) and write the DB (and clear the dirty flag) after three seconds or so. This way, a short burst of multiple events that would need to flush the DB to disk would only result in one write instead of many (also relevant for the limited write cycles on flash-based storage, as in some netbooks and maemo devices). Do you think that would be overkill? Of course, we should do some benchmark with the patches that we produce for this. -- 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
