Darktable v5.0.1 is painfully slow at startup and import of photos

I had a darktable v5.0.0 installed.
I seldomly reboot my computer, but instead lets the system go into std.by.
As usual I resumed from st.by as normal, but this time I had left DT 5.0.0 open. When I switched to it, it was slow, and I killet the proces with taskmanager.

I tried to reopen it, but it seemed to hang on the Preparing database screen. So I again killed the proces from Task manager. I did not see any hints in the Windows log files…
C:\Windows\System32\winevt\Logs

So I downloaded the newest DT 5.0.1. and installed this.
It also hung on startup, but this time I let it go through the proces of preparing the DB. And it asked me if I wanted to delete the DB lock files, which I confirmed. And it finally opened, but is painfully slow.

My system is a fast system, which I have a lot of experience with former DT versions using. It has always been a zippy experience. But now things are unusably slow. And I cannot use it.
I have now disabled the check for changed sidecar files (but with no change with the slow startup). As I usually only change photos in DT itself.

Do any of you guys have any hints to why my DT has become so slow…?

Any help appreciated…

Best regards to all of you inspirational souls

Start darktable from the command line with debug option -d common. See darktable’s FAQ for information how to do that on Windows. The resulting log file might give some information what is slowing down the app.

1 Like

What would happen if you made a duplicate shortcut and edit the command line… add --configdir “path” and create a folder and substitute that for where I typed path…this will run DT with a brand new clean db…if it speeds up then your install is likely okay and then the debug info noted by @pehar might be what you need to dive in to…

Hmmm - after a few more close/opens of DT, it appears to be back to its snappy self.
Thanks for this awesome program.

2 Likes