It would be nice to have a starting screen as soon as we start dt. Anything, could be a 50x50 pixel darktable logo. I'm an old nervous man ;) so on my old computer if I don't see anything happening on the screen I quite often start a second instance of dt.
HP Elitebook 850 G2, Windows 10, i5 5300U 2,3GHz vpro, 8GB memory, connected external 2TB drive via USB 3.0
After restarting computer, only FF working, waiting few minutes before starting dt it takes about 15s to get white window with darktable on bar and 30s to see program with all modules and empty boxes for miniatures of photos quite fast restored. tested once, I'll restart computer again and if the time change I'll write you.
Closing dt and rerunning gives white window in 3s and full running in circa 6,2s. tested couple times, same result each time.
Unchecked "look for updated" - doesn't speed up. I checked also on my old Dell Optiplex 780, core2duo with 4GB, Win 10 and AMD Radeon HD 7500 1GB, same ext HD connected via USB 2.0. First start takes 22-23s, every next start below 6s. It's faster than laptop with (theoretically) much better components. Tested three times (computer reboot).
#7 Updated by Tobias Ellinghaus 13 days ago
Could you try starting darktable from a cmd.exe shell with the "-d control" command line parameter. Then have a look at the output, does is show new lines all the time while starting, or is it waiting somewhere?
If that doesn't work I will look into providing a test installer that outputs some timing of the startup process.
I don't get any printout with -d control. To check if calling darktable with options works I checked disabling opencl (opencl is disabled) and --version swith.
this is darktable 2.4.1
copyright (c) 2009-2018 johannes hanika
bit depth is 64 bit
SSE2 optimized codepath enabled
OpenMP support enabled
OpenCL support enabled
Lua support enabled, API version 5.0.0
Colord support disabled
gPhoto2 support enabled
GraphicsMagick support enabled
OpenEXR support enabled
D:\Program\darktable\bin>D:\Program\darktable\bin\darktable -d control
#9 Updated by Tobias Ellinghaus 10 days ago
Ah right, the -d stuff is written to the log file on Windows, which of course doesn't help with getting timing information. Stay tuned, I will come up with something.
https://www.darktable.org/about/faq/#faq-windows-logs tells where to find the log files.
Edit: Actually, have a look in the log file and look for "[init] startup took".
on desktop Dell
first start: [init] startup took 16,632923 seconds
restarting darktable: [init] startup took 4,408072 seconds
On laptop HP
[init] startup took 23,612731 seconds
[init] startup took 5,847194 seconds
First start takes few seconds more than stated in report. Second start is circa 1-1.5s longer. Measured from moment of hitting enter to moment having photos displayed on screen.
#12 Updated by Tobias Ellinghaus 1 day ago
Please grab the new 2.4.2 from , install it and run
darktable -d control. Then have a look at the log file and show me the timings until the startup is finished.
#13 Updated by Peter M about 2 hours ago
Made two files. After first run I deleted file and subsequent start log file has "2" suffix in name.
Off-topic: why I don't see directory INetCache? The only way to access log file is to run search file from FreeCommander (great alternative to Total Commander). I marked "show hidden files" so I can get up to directory Windows inside which should be INetCache.