[Digikam-users] Re: digikam search and high cpu usage: sqlite, mysql compared

[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
-- 
View this message in context: http://digikam.1695700.n4.nabble.com/digikam-search-and-high-cpu-usage-sqlite-mysql-compared-tp3174598p3175810.html
Sent from the digikam-users mailing list archive at Nabble.com.