Hello Thomas, well, for me this patch at least decreases the (too ?) high CPU load that gPodder caused when downloading from many channels @ high speed. As far as I am concerned, polling interval could be longer - downloading a podcast in my case typically involves files between 50 and 150 MB, so it usually takes several minutes, and I do not watch the progress continuously, so for me an update every 10 seconds would be just as fine. I leave it to your discretion - the patch works OK for me, we'll have to see what other users say. Thanks, Wilfred --- Thomas Perl <thp at perli.net> wrote: > Hello, Wilfred! > > On Wed, 2007-10-03 at 17:08 -0700, Wilfred van > Rooijen wrote: > > I patched the files and am currently downloading @ > 650 > > kB/s, which is the max my wi-fi will put through. > CPU > > still runs @ 100% speed, but overall load is much > > lighter than before. The CPU temp is around 60C, > which > > is not abnormal for light loads. This patch solves > the > > (insane) CPU loads that gpodder caused earlier, > and as > > far as I am concerned, the counters still seem > > responsive enough. > > So, this fixes your problem or should I try to > optimize it a bit more? > > Thomas > > _______________________________________________ > gpodder-devel mailing list > gpodder-devel at lists.berlios.de > https://lists.berlios.de/mailman/listinfo/gpodder-devel > ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/