Quote:
Originally Posted by TenaciousBadger
i wonder what the lag would be if i had 3000...
|
Probably about the same.
Calibre has two start-up phases. The first is simply starting calibre, and consists of the time between when you say 'go' and when the splash icon appears. The second is opening the DB, and consists of the time between displaying the splash icon and the books.
The first phase takes time because calibre consists of around 1,000 separate small program files, plus some larger ones. Calibre must open many (if not most) of these before it can say "hello". If you start calibre, wait, quit, and then immediately start again, the first phase should be faster, because most of the files it needs will already be in memory.
The second phase time depends on the number of books. You shouldn't see anything significant (more than 1 or 2 seconds) until you reach thousands of books. For example, on my machine with 1000 books in my library, this phase takes around 2 seconds.
You can easily see the separation between the times by running calibre in debug mode. It prints a message when it starts, and then prints the amount of time it took to open the library. To run calibre in debug mode, open a command box (or terminal), then type "calibre-debug -g" (without the quotes). The time until "starting up..." is phase 1. Phase two time is displayed next.