One thing I've noticed is that if I restart calibre with ctrl+shift+R the start times are +10secs whereas running calibre-debug from the command line with the output appended to a pre-existing calibre.log are 2-3secs (which is the same as a normal start),
The log file that's created when ctrl+shift+R is used to run in calibre-debug IS in the Windows Temp folder. But the calibre.log file which is used when I run the calibre-debug command (via a one line batch file) IS NOT in the Windows Temp folder.
I use the CALIBRE_TEMP_DIR environment variable to relocate calibre's transient temporary folder - into the same parent directory as my calibre.log file, which is at the root of my SSD system drive.
So I tried disabling the CALIBRE_TEMP_DIR directive, made no difference, its still 2-3 secs, except when I use ctrl+shift+R.
One thing I have noticed (and I think its only been recently) is that calibre sometimes doesn't push itself to be topmost window when I start it. I start calibre from the taskbar, which is configured to work a bit like a 'quick launch' bar, but with stacked icons, no previews, and no silly start button. I haven't detected a pattern; its a very minor irritant - Windows+4 will make it topmost.
BR
|