Hello, Wilfred! On Tue, 2007-09-25 at 16:40 -0700, Wilfred van Rooijen wrote: > An observation using the latest version of gPodder: downloading is > very resource intensive now (or so it seems). I have a laptop with CPU > throttling. I am downloading 5 streams @ 100 KB/s each, and the CPU > goes to full speed (1.6 GHz), CPU indicator shows close to 100% > constantly and ACPI CPU temp goes up from about 45 C (normal idle > temp) to 76 C (normal temp during full use). The older version of > gPodder got the streams at almost the same bandwidth, but did > not use that much CPU-time. Any ideas? I'm convinced that some process > is doing some busy waiting somewhere during the downloads.
I think the problem is related to gPodder doing status updates more often than previously, and the GTK interface has to keep up with the constant flow of GUI updates (window title and the "downloads" tree model + tree view). I've tried porting gPodder to Windows yesterday, and running on my 1.7GHz Pentium IV-M, I was able to see these "hanging" problems on Win32 when downloading from a local server. It doesn't happen to me on Linux (I'm having my download queue set to 1) and if doesn't happen when downloading _anything_ from the Internet, because with my previous 64k line, I can't get anything beyond 8kb/s, so there cannot possibly be more GUI updates than that :) That being said, I think I could try to limit the number of GUI updates by filtering the messages sent to the GUI for updating the interface. I would need you to check out the SVN repository, apply patches to it that I send you and you test if things work with a high-speed internet connection. Would you like to help here? Thomas _______________________________________________ gpodder-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-devel
