Hello,
As I add, remove, copy, move to other place... a lot in my digikam albums I thought it was a good idea to clean the database. So after copying digikam4.db and thumbnails-digikam.db I started the job via tools->datebase->cleanup, all three options clicked (sorry, I have it in german, and can't check the menu as digikam is frozen). So it started happily but since 3 hours it is stuck showing "clean up the databases: ordening main database ("Hauptdatenbank aufräumen") 98% The process table shows digikam with 12% CPU and 625000K memory, 80000 K shared memory (memory number changes from time to time, but CPU% is always 12%) I see that digikam4.db was updated the last time at 14:56h and has the same size as my backup. Digikam is frozen since a long time (hours). I wonder if I should leave it for more weeks or years :-) or if I should close digikam and forget about database optimization? It's digikam 6.0 on opensuse 43.3 digikam4.db has only 150MB, thumbnails-digikam.db 6GB (last updated at 11:58h, same size as backup version). -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com |
Yes, that's right.
I had the same thing in 5.9. If you have a backup you can abort, if not DK will become extremely unhappy. Most of the time is rebuilding the thumbnails. I did it last late last year with 40,000+ images and it took about 22 hours (my thumbnail file is around 2.5gb). I was using htop to monitor. On Thu, 14 Mar 2019 16:35:12 +0100 Daniel Bauer <[hidden email]> wrote: > Hello, > > As I add, remove, copy, move to other place... a lot in my digikam > albums I thought it was a good idea to clean the database. > > So after copying digikam4.db and thumbnails-digikam.db I started > the job via tools->datebase->cleanup, all three options clicked > (sorry, I have it in german, and can't check the menu as digikam is > frozen). > > So it started happily but since 3 hours it is stuck showing "clean > up the databases: ordening main database ("Hauptdatenbank > aufräumen") 98% > > The process table shows digikam with 12% CPU and 625000K memory, > 80000 K shared memory (memory number changes from time to time, but > CPU% is always 12%) > > I see that digikam4.db was updated the last time at 14:56h and has > the same size as my backup. > > Digikam is frozen since a long time (hours). > > I wonder if I should leave it for more weeks or years :-) or if I > should close digikam and forget about database optimization? > > It's digikam 6.0 on opensuse 43.3 > digikam4.db has only 150MB, thumbnails-digikam.db 6GB (last updated > at 11:58h, same size as backup version). -- > Daniel Bauer photographer Basel Málaga > https://www.patreon.com/danielbauer > https://www.daniel-bauer.com -- sknahT vyS |
Free forum by Nabble | Edit this page |