digikam search and high cpu usage: sqlite, mysql compared

[Elle Stone]

Dear digikam users,

I upgraded from Ubuntu 10.4 to 10.10 and installed digikam 1.7 (many
thanks to Philip Johnsson's ppa). I'm still trying to figure out how
to actually use digikam, so please bear with me.

I have digikam running mysql and also sqlite, by means of stopping
digikam, renaming the .kde folder in my home directory to change from
using sqlite to using mysql, and vice versa, and then restarting
digikam.

I'm not actually accomplishing anything in digikam (otherwise running
two databases would be stupid, of course), just trying out the
different digikam functionalities on a collection of jpegs, all of
which have embedded tags, copyright, etc.

One functionality I've played with is search. Search and tag filter
under sqlite seems reasonably responsive.

Search and tag filter under mysql also happens quickly, but for some
reason the cpu usage goes up to 100% and stays there until I leave the
search results. Searching using the left side pane and only a single
keyword search seems to not have this problem so much. Using the
bottom search box or the tag filter definitely spikes the cpu up to
100% and it just stays there. Ditto with the tag filter. And trying
more complicated searches using the left side pane advanced search
also send the cpu to 100%, where it stays until I leave the search
results.

Anyone else noticed this problem? Any insight as to how to make the
cpu usage drop back to normal when the search is completed? As I said,
the search itself is very quick. And under sqlite the cpu drops when
the search results are in. mostly.

Thanks in advance for advice on Search and/or digikam/mysql,
Elle Stone
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Elle Stone]

Hmm, I was wrong. The problem happens equally in mysql and squlite.

(1)Using the search bar at the bottom of the page to enter search terms, then (2)clicking on the search icon at the top of the page to do the search, sends the cpu to 100%, where it stays, permanently, even after the search results have been retrieved.

The search results show up very quickly. My test database of images is not that big. Why does the cpu stay pegged? The only way to get the cpu usage to drop is to leave the search results, which kinda negates the whole point of searching in the first place.

Elle Stone

[Elle Stone]

Is digikam searching the database AND the image metadata? Or just the
database? If it is searching the image metadata in each and every
image, that would cause the high cpu usage  And a lot of unnecessary
disk activity.

Unlike what I thought at first, this is not an sqlite vs mysql
problem. Rather the cpu usage spikes on most/all searches regardless
of which type of database is being used. The search results come up
very quickly. But the cpu usage stays high for a very long time after
the search is actually and obviously completed.

As I stated earlier,

(1)Using the search bar at the bottom of the page to enter search terms,
then (2)clicking on the search icon at the top of the page to do the search,
sends the cpu to 100%, where it stays, permanently, even after the search
results have been retrieved.

Actually the cpu usage does stop eventually, if I wait long enough. I
just don't like to see my processor thrashing for no discernible
reason.

Any help greatly appreciated. This high cpu usage that accomplishes
nothing is quite disappointing.

Regards,
Elle Stone
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2011/1/5 Elle Stone <[hidden email]>

Is digikam searching the database AND the image metadata? Or just the
database? If it is searching the image metadata in each and every
image, that would cause the high cpu usage  And a lot of unnecessary
disk activity.

Just in Database. A copy of most important metadata tags from image are duplicated in database file.

Gilles Caulier
 

Unlike what I thought at first, this is not an sqlite vs mysql
problem. Rather the cpu usage spikes on most/all searches regardless
of which type of database is being used. The search results come up
very quickly. But the cpu usage stays high for a very long time after
the search is actually and obviously completed.

As I stated earlier,

(1)Using the search bar at the bottom of the page to enter search terms,
then (2)clicking on the search icon at the top of the page to do the search,
sends the cpu to 100%, where it stays, permanently, even after the search
results have been retrieved.

Actually the cpu usage does stop eventually, if I wait long enough. I
just don't like to see my processor thrashing for no discernible
reason.

Any help greatly appreciated. This high cpu usage that accomplishes
nothing is quite disappointing.

Regards,
Elle Stone

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users