------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From frank.osterfeld kdemail net 2005-07-31 12:04 -------
> Is it possible to post a patch that returns usability from the 3.4.0-version
> (remember filter when starting up/shutting down, remember filter when
> changing feeds and make the new & unread filter work again without selecting > an other filter first)?
Except for saving filters on shutdown, this should work with the patch above? What do you mean with "make the new & unread filter work again"?
> but during upgrade in the _stable_ series it became one of my biggest annoyances.
Because of this issue? Or are there other regressions I am not aware of?
>It really makes me wonder if you use this version yourself and how many feeds
you have? Do you think the current stable version is usable (with many feeds)?
There are some performance-related issues with many feeds in the stable version:
1) slow startup, huge memory consumption. This is improved in SVN, but can't be fixed in the 3.4.x series. (as it needs major changes)
2) slow rendering of the article list: Filling the list with articles, was extremely slow, due to adding the article headers to the list in a stupid way. This fixed in 3.4.2. (from 40 secs down to 4 here)
3) related to 2), if a user has "All Feeds" (or any other folder with many feeds/articles) selected and fetching starts, Akregator eats all your CPU and freezes. This is because every feed fetched causes the article list to be completely cleared and refilled. (e.g. 40 seconds * 40 feeds = 1600 seconds full CPU usage) This should be improved in 3.4.x because of the fix for 2). In SVN, we avoid complete rebuilding of the article list and the problem should be gone there entirely.
To avoid the problem, never select "All Feeds"...
Ok, this is all performance related. Now to the quick filter. If I understand you correctly, the filter problem has nothing to do with performance (where it shouldn't have a deep impact), but the way you use Akregator to read articles.
Maybe our "usage patterns" differ, so let me describe how I use it (having 88 feeds, with 34213 archived articles in total):
- I mostly read articles "feed-wise", selecting single feeds and looking what's new. As the new items are usually on top here, I don't need a filter. I just scan the list and sometimes use +/- shortcuts to walk through unread articles.
And for folders, usually there are too much unread articles, as "show me all unread articles for Folder X" would make sense. I am rarely interested in all the unread items in a folder at once, as there are many relatively unrelated "high-traffic feeds" (CVS commits, wiki changes...) in it. So I prefer to read the items feed-wise.
- Actually I select folders only for searching, and I almost never use the status filter except for listing flagged articles.
On the other hand, I understand that people want to see unread articles only, or see everything unread in one list. As "show me all the new stuff" is a central use case and it should be possible do get that conveniently. I guess this is how you use it?
Some ideas to improve the filtering for new items:
- make the filter thing configurable.
- make it possible to sort the article list by status (this was already requested by usability folks)
- add special nodes like "Unread articles" to the feed list to filter for the state. This would be more intuitive than selecting "all feeds" and setting the quick filter. The drawback is that you can't select specific folders or feeds this way.