Bug 174147 - search filter is slow, scalability problem
Summary: search filter is slow, scalability problem
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-03 05:51 UTC by Simon80
Modified: 2017-01-07 22:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
callgrind dump of a small portion of a very long search (40.22 KB, application/x-gzip)
2008-11-03 06:05 UTC, Simon80
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Simon80 2008-11-03 05:51:32 UTC
Version:           1.3.1 (using 4.1.2 (KDE 4.1.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.27-7-generic

To reproduce this, click on "All Feeds", then click on the search textbox and paste a word into it. If you have a large enough number of archived items, you'll see that this takes more CPU time than it should.
Comment 1 Simon80 2008-11-03 06:05:45 UTC
Created attachment 28290 [details]
callgrind dump of a small portion of a very long search

I don't know if it's useful to attach a callgrind dump, since the developer may want to just make their own selectively, but here is one. I took two, and it looks like the second one (this one) contains info about more time-consuming misbehaviour that hadn't started during the first dump's timespan. I'd like to add that the UI is unresponsive during the search, so the time isn't being wasted providing user feedback, it's just being wasted.
Comment 2 Denis Kurz 2016-09-24 19:42:24 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:18:45 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.