I was still intrigued so I decided to see what actually makes calibre tick.
To avoid extra delays on starting up, I let calibre point by default to an almost empty library (2 books, of which 1 is just a dummy). By the way, this is also my normal manner to start calibre so the freeze is kept to a minimum. Thereafter I rebooted, started tracing using Process Monitor (
www.sysinternals.com) and then I did run calibre (without options).
The results where as follows:
1 - Most accessed (obvious) pylib.zip
2 - catroot (windows updates directory)
3 - Quality Check.zip
4 - all (windows) font files
5 - metadata.db
(4) is annoying. When you have a lot of font files (and you will when you use all kinds of editing tools as they all tend to place new fonts there) they all will be traversed which just consumes precious time. Perhaps a Qt setting?
(2) is weird. What has calibre to do with windows updates? They are all traversed which is using up a lot of system time and will happen *
only* when starting calibre for the first time. Further, the only difference I see between 2 succeeding runs of calibre is the access to catroot.
See the attachment for further details.
Just my 2cts.