|
Just FYI, you can startup calibre in debug mode, calibre-debug -g from a command prompt/terminal and it will print the startup time.
When you are measuring startup times, be sure to distinguish between cold and hot startups. Because calibre includes its own DLL files, these are often not in the OS cache on first startup, therefore, first startup times are typically much longer than subsequent startup times. The vast majority of calibre startup times (for libraries of a few thousand books) is actually spent loading DLLs and initializaing state.
Things that can really affect startup time on windows are lots of accumulated windows updates (use disk cleaner to remove old ones) and antivirus programs that slow down loading of files from the calibre installation and temporary folders.
Finally, as more anecdata, calibre starts up with my thousand book library in under a second (0.93 +- 0.05 over ten hot starts) on a three year old machine (albeit with a SSD and /tmp in RAM).
|