Bug 169108 - Very high cpu usage
Summary: Very high cpu usage
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-14 10:28 UTC by Simone Lazzaris
Modified: 2009-04-24 11:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simone Lazzaris 2008-08-14 10:28:22 UTC
Version:            (using KDE 4.1.0)
Installed from:    Unspecified Linux
OS:                Linux

I'm using the new akregator 1.2.50 on kde 4.1, arch linux standard binary. I notice a very very high cpu and memory usage.

Where iconized in the tray, akregator is using 18.9% of my 1024MB memory (according to top). I think that it's an INSANE quantity of memory just to sit in the tray.

When I'm viewing the feeds, the CPU usage baloons, up to 100% while downloading the feeds, and it's very very slugghish at that.

On the very same system, the akregator version that came with kde 3.5.9 used to be snappy.
Comment 1 Augie DeHainaut 2008-09-08 12:54:47 UTC
I'm getting this too.  4.1.1 on Kubuntu
Comment 2 Frank Osterfeld 2008-09-08 19:27:33 UTC
Please test memory usage with 4.1.1. It should be better.
For CPU, there is a fix in trunk/scheduled for 4.1.2 which should improve the situation. Feedback appreciated (when 4.1.2 is out).
Comment 3 Simone Lazzaris 2008-09-09 14:19:40 UTC
I've tried version 4.1.1 (arch linux i686 binaries), and, while it seems better (but it can be an impression) once the feeds have been read, still it uses 99% CPU to fetch them. 
As the feeds have been obtained, the usage drops to 4-5%.
It seems better, but I can't say it's solved. If you think that the trunk version could be better, and that the test is significant, I can try to download and compile that one.
Comment 4 Frank Osterfeld 2008-09-09 18:16:49 UTC
Yes, the fix that should lower CPU usage went in after 4.1.1. 4.1.1 already fixes some memory leaks though.
Comment 5 Simone Lazzaris 2009-04-24 11:49:56 UTC
The behaviour is now correct (kde 4.2.2, akregator 1.4.2).
I think I can close the bug.