|
The issue of calibre’s startup speed shows up in this forum quite regularly. It seems to me that the obvious slowness of calibre startup (and some other of its functions) is quite choking for new users. The community here is one of the friendliest and helpings one can find on the net. However, the zeal takes sometimes the best of some of us.
There is no need to tell a newcomer that the slowness of calibre is just in his imagination, that other program starts just as slow, etc.
Calibre is slow. Period. It used to be really slow, but the situation has improved a lot and hopefully this trend is going to continue in future releases.
I personally do not care much about the startup speed, but if it is of concern to you, there are a couple of things you could check.
1- Your security software. I would exclude calibre main dir and calibrelibrary from the realtime protection. You should scan however, every new book by hand before adding it to the library.
2- Consider disabling “check for new version” and reducing the network timeout.
3- Job priority.
3- Number of worker processes and the limit simultaneous jobs.
On my system (WinXP on a Core2 Duo @ 2.66 GHz, 2 GB RAM) with a library of 300 books and no news sources, calibre takes some 20 sec to start the first time and after, less than 2 sec on a particular PC startup session. During that first run, the main calibre proc may take up to 150 MB of RAM. After that, it stabilizes around 20 MB. The use of RAM of each of the 4 calibre-parallel procs is stable around 29 MB.
|