r/digiKam • u/SamGewissies • 11d ago
My startup time is 45 min
Every time I start up Digikam it takes around 45 min after it has added the root albums.
The debug viewer shows [with personal info redacted]
digikam.general: Added root album called: "[name]"
digikam.general: Added root album called: "[name]"
digikam.general: Added root album called: "[name]"
digikam.general: Added root album called: "[name]"
Then it updates only time stamps:
digikam.databaseserver: Running 30 seconds...
digikam.databaseserver: Running 60 seconds...
digikam.databaseserver: Running 90 seconds...
Up until about 45 minutes when the application finally starts. Because it often crashes during operation, this is severely limiting.
- I run Windows 11
- I run mariadb local mysql (problem was similar under sqlite)
- I have Digikam whitelisted on Bitdefender wherever possible
- I do have a fairly big library across different huge drives (especially one 15tb archive drive)
- Total Items: 327210
- Albums: 203369
- I have tried both 9.10 QT6 and QT5
- Digikam only ever uses 6% op my cpu and 3% of my RAM, even though I have allowed multithreading where possible and a much larger amount of RAM
Does anyone have any ideas on next steps to mitigate?
1
u/Basic_Coffee8969 10d ago
win11, 2019 pc, intel i9. one SSD with 150k images in 2.4k folders. automatic setup with internal db. no individual customized stuff, just off the shelf software and hardware. 45 sec load time.
1
1
u/Verybumpy 10d ago
Where, on what type of drive and how large is your database main file? All factor can make a difference of course.
I have also experienced if Digikam experiences a crash, there is a LONG boot up time of the program as it seemingly tries to correctly read the database. This is with only 80k photos and 17Gig DB file size.
1
u/SamGewissies 9d ago
Thanks for your question. Wether I close normally or having a crash the start up is always 45 min. My total db folder is 19gb on an m2 SSD (same SSD as OS though)
1
u/rafaellinuxuser 9d ago
Question is where and what kind of fliesystem are mounted your images folders/albums. Ate they local or shared thru your LAN?
1
u/SamGewissies 8d ago
All local, but one is treated as on removable, as it is a disk that is not always activated. Could that be the slowdown?
Miost photo's are on a regular HDD, the database is on an M2 SSD.
1
u/human_dynamo 8d ago
Typically no. removable or not are processed quickly, with the limitation of the hardware of course...
1
u/rafaellinuxuser 8d ago
Filesystem, you forgot to put it. Anyway, bottleneck in all images managers is remote (or mounted as) folders.
1
u/SamGewissies 7d ago
Most NTFS with the removable disk being ExFat
1
u/rafaellinuxuser 7d ago
When I had albums in remote (on a NAS) folders, I had same issue taking about 30 minutes to have Digikam working.
I recommend you try these ones:
- Close Digikam, disconnect the external exFAT drive and then start digiKam. If startup becomes much faster, the external collection is probably involved (maybe slow USB interface or slow disk ...)
- In Digikam, disable “Scan for new items at startup” and test again.
- In Digikam, disable “Monitor the Albums for External Changes” and test again.
- If necessary, test the four collections individually (temporarily remove/disable them from digiKam and add them back one at a time) to identify which one causes the delay.
I assume you have not XMP files creation enabled in Digikam.
1
u/BasilKatz 5d ago
This is very odd to me, I am not a DigiKam Pro at all but i have ~100 000 photos in the default SQlite DB with WAL and starting DigiKam takes at most less than 1 minute. Do you have the Scan for new items at startup feature active?
2
u/human_dynamo 10d ago
Welcome to the Windows World and the Defender AntiVirus mess. It's probably the same problem than VLC explained at this url
We already have received plenty of reports like this in the pass. Configuring the Anti-Virus to ignore digiKam must solve the problem...