| Summary: | search gets really sluggish while typing search string | ||
|---|---|---|---|
| Product: | [Applications] juk | Reporter: | Juha Kuikka <kuikka-kde> |
| Component: | general | Assignee: | Scott Wheeler <wheeler> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Juha Kuikka
2003-11-04 22:54:48 UTC
Seems that the bug database did not save my platform's information: I'm running Debian unstable with Juk from debian package also. I also forgot to mention that I have ~4400 songs in my Collection list and browsing it (without search) it very fast. Ok, and you're sure that you're running KDE 3.1.4 not, i.e. 3.1.3? There was a bug in one of KDE's libraries that I fixed in painting lists that I think wasn't in KDE 3.1.3, but made it into 3.1.4. Oh, and also what's the CPU on the machine? Right, It seems there is an error in kde packages in debian. Every About dialog tells me that I'm running kde 3.1.4 but packages have mixed version numbers, for example: kdebase 3.1.3-1 kdelibs-bin 3.1.4-2 So no, I'm not sure what version I have. :) CPU is 1.2G athlon thunderbird with 1G memory. Ok, I'll give a description of what the bug was in pre-3.1.4 and we'll see if it fits. It's a little bit strange, but I'll try to explain. :-) Searching gets especially slow when items are far apart. When you search JuK is just hiding the items that don't match -- they're actually still in the list. Well, there are some calculations that happen when painting to figure out what the next item is. Before some of my fixes to the libraries these were very slow; they're much faster now. So, this problem became the most evident when there was a lot of space between the matched items. i.e. if when the search is empty these items might normally be separated by 100 or 1000 items or something. Can you try various sorting combinations to see if this fits? (Or if it even makes sense?) It doesn't seem to be this problem. I tried it by creating some mp3's with the same title name but albums 'aaa' and 'zzzz'. Then I searched for those by title. I also compiled the 3.2beta1 kde from sources and it seems the slowdown I initially described is still there but it is not as radical. Juk version seems to be 2.0beta2. When you add this last key that you mention does it significantly reduce the number of matches? What column are you sorting by? (I know these are weird questions, but they're related to some of the kdelibs internals and *might* give me a clue as to what's going on.) As I reported in my initial raport, there are 12 songs before I add the last key. After that there are 8 songs. Sorting is by Artist. I'm glad to report that this sluggishness is gone in Kde 3.2beta2 version of Juk. Also JUK's search seems to be much quicker overall. Great work. Closing this bug as Juk included in Kde 3.2Beta2 releases does not have this bug anymore. Ah, great. This makes me feel better about not being able to find a way to reproduce it. :-) (I suspect it was something that I fixed by accident along the way in the process of working on other optimizations.) |