| Summary: | deleting or moving a bookmark can take FOUR SECONDS OF CPU TIME on an Athlon XP 2000+ system. | ||
|---|---|---|---|
| Product: | [Applications] keditbookmarks | Reporter: | Peter Grandi <pg_kde> |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | contact |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Peter Grandi
2005-08-26 16:41:45 UTC
Speaking with some people on '#KDE-devel', their impression is that most of the time is taken by writing out the whole bookmarks file in XML more than by redisplay, which is also an issue. Well 6000 bookmarks is probably a little insane. Profiling seemed to indicate that elimanating a few calls to KBookmark::address() could make a difference, as a lot of time was spend in it. I even have a few ideas how to improve it, but I currently don't have the time to work on it. It might be enough to allow choosing explicit saves, where saving the bookmark list does not take place after every single operation. I don't mind waiting a bit every now and then when I save the list. But several seconds of pause on every change is pretty appalling. «Isn't a duplicate of bug 59401?» Yes, it looks like it is a duplicate, so linked them, even if bug 59401 was initially misdiagnosed as a broadcast-update issue. It is instead very clearly a save-data slowness issue. I am marking this as a duplicate and then I'll add some new information to it. *** This bug has been marked as a duplicate of bug 59401 *** |